Migration from Super Table: Between legacy hurdles and Craft 5 core features

Anyone who thinks a Craft upgrade is done with a single Composer command will quickly learn otherwise when Super Table is involved.

Super Table was an indispensable tool in Craft projects for years. With Craft 5, that has changed: the functionality is now part of the Craft CMS core, and the plugin itself is being phased out. What sounds straightforward is in practice one of the most error-prone migrations a Craft project can go through. Underestimate it, and you risk data loss, broken field structures, and a relaunch timeline that evaporates into thin air.

Why is Super Table End-of-Life a critical event for existing projects?

Super Table was never a minor utility plugin. It was deeply embedded in editorial structures, used for tabular content, nested layouts, and complex input interfaces. The developer Verbb has officially communicated its end-of-life. No new features are coming. Security updates will be finite. Anyone still running active projects on Super Table today is sitting on a structure with no future.

The architecture of Craft 5 is fundamentally new. Matrix blocks are now fully-fledged entries, and native fields replace the plugin. It sounds clean. The problem lies in what came before.

What specific errors occur when upgrading from Craft 3 to Craft 4?

The jump from Craft 3 to Craft 4 is often the first stumbling block, long before Craft 5 is even in sight. Moving from PHP 7.4 to PHP 8 introduces typing changes that knock Super Table off balance in many installations. Database inconsistencies that were silently tolerated in Craft 3 become immediately visible during migration. And anyone who used Super Table inside Matrix fields will often encounter the first hard crash right here.

The most common sources of error:

• Missing UUIDs in older Super Table instances abort the migration process and leave behind unusable field configurations.
• Database inconsistencies from Craft 3 cause SQL errors in nested structures that are nearly impossible to predict manually.
• Complex nesting (Super Table inside Matrix inside Matrix) regularly overwhelms automated migration scripts, causing relations to be lost in the process.
• Layout losses occur because the compact table view of Super Table cannot be directly reproduced in Craft 5, requiring editorial UIs to be rebuilt from scratch.
• Dependency hell caused by deeply intertwined plugin dependencies often prevents even a clean update to Craft 4 as an intermediate step.

What changes fundamentally with Craft 5, and why do automated migrations fail so often?

Craft 5 changes the data architecture from the ground up. The decision to treat Matrix blocks as fully-fledged entries transforms the entire data architecture. Super Table has built a parallel structure over the years that cannot simply be translated. Automated conversions fail precisely where it hurts the most: in the fields that were used most intensively. What looks like a minor technical detail is in practice often a multi-day intervention in the database structure.

Automated conversions are the wrong approach. Anyone who has made extensive use of Super Table needs a structured analysis of their fields, clean backups, a local test setup, and in most cases a manual refactoring of the database structures. That's not pessimism — that's the realistic state of affairs.

What strategy actually minimizes the risk when migrating to Craft 5?

There is no risk-free migration, but there is smart preparation. An audit of the existing field structure reveals which Super Table fields are still genuinely needed and which have been carried along unused for years. Local testing with tools like DDEV catches SQL errors before they cause damage in the production environment. And for deeply nested structures, a dedicated Craft module for data migration is more reliable than any automatic update routine. The effort is real — but it is plannable.

A migration approached half-heartedly at this stage costs more time than careful preparation. This is especially true for agencies that treat Craft as just one of many technologies in their portfolio and don't know the specific pitfalls of Super Table from first-hand experience.

When is it worth bringing in external support?

Not every agency and not every developer has the depth of Craft CMS expertise needed to safely guide this migration. That's not a criticism — it's a reality of the market. Super Table migrations regularly fail not due to lack of effort, but due to lack of hands-on experience with exactly this type of error. Recognizing the signs early saves costly rework and prevents an upgrade project from turning into an unplanned rebuild.

Craft unit has guided upgrades of this kind many times — analyzing complex structures, migrating data cleanly, and redesigning field layouts for Craft 5. If you're facing these challenges and aren't sure how to handle the transition cleanly, speak with us. An initial conversation is non-binding.