Migrating from Flux and Mask to Content Blocks in TYPO3 14

Flux is discontinued and Mask does not run on TYPO3 14. Here is how we migrate legacy content elements to Content Blocks, the modern core-aligned standard.

If your TYPO3 site uses Flux (fluidcontent/fluidpages) or Mask for custom content elements, TYPO3 14 is the moment to migrate. Flux is discontinued and Mask does not run on v14 — the modern, core-aligned replacement is Content Blocks.

Why Content Blocks

Content Blocks let you define custom content elements as self-contained packages: fields, template and configuration in one place. There is no fragile hand-written TCA, elements are reusable across projects, and the approach follows the direction of TYPO3 core.

Migrating from Mask

Mask stores its fields in dedicated columns. We recreate each Mask element as a Content Block with matching fields, migrate the existing content into the new structure, and reuse native tt_content where possible — so editors keep their content and workflows.

Migrating from Flux

Flux-based content elements and page templates are converted to Backend Layouts plus Content Blocks. Grid and field definitions move into the new elements, and the data is migrated so the frontend output stays consistent.

The result

After migration you have clean, maintainable content elements on a supported foundation, ready for TYPO3 14 and beyond. See our TYPO3 development service or contact us to plan your migration.