A platform choice is a ten-year commitment made with bad information. Before you commit, we stand up a representative slice of your real site in each destination you're considering — Drupal 11, TYPO3, WordPress, Wagtail, SharePoint, Contentful, Sanity, Backdrop — so you compare your own content, structure and editorial workflow. You pick; we migrate the rest to the winner.
Previews are faithful, not mock-ups: every route is round-trip verified, and your content is shown coming back OUT — the exit, not just the entrance.
One neutral engine reads your site once and writes it into every candidate, so evaluating three targets doesn't cost three migrations. Every route below is live tooling, round-trip proven.
The full legacy long tail: fields with their permissions and option lists, webforms, Panels, editorial workflows, menus, aliases. Original ids and uids preserved. Drupal 7 is a source only — it reached end of life in January 2025, and nothing migrates onto it. Backdrop, its living fork, is a destination as well.
Both directions, live-verified: content and config, roles and field permissions regranted, menus with hierarchy, media bytes. 50,000 nodes moved with their original ids intact.
In and out. ACF models map faithfully; Elementor and Gutenberg pages cross as designs, not screenshots — and can even convert between the two builders in place.
Lists, libraries, term sets and modern pages, both directions. Lookups stay references, people stay people, and site navigation lands as real navigation.
Both directions. The page tree lands as a page tree, content elements stay content elements, inline items stay inline, and files come back as real FAL references with their alt text. Read without booting the CMS, so an install too old to run its own tooling is still readable — and written to 14.3 LTS, the version with a support runway.
Both directions, verified round-trip on Wagtail’s own demo site. The page tree lands as a real page tree, repeating content becomes StreamField blocks, and rich text crosses in Wagtail’s native forms — images as true embeds, not pasted markup. Written to 7.4 LTS, the version with a support runway.
Headless, in and out: content models, rich-text documents and assets cross with string ids preserved exactly — a round trip returns the same ids it left with.
Page-builder layouts share one structural model inside the engine, so a page composed in Elementor can land as native Gutenberg blocks or a SharePoint canvas — and back.
Every route is gated on a round trip: out, back, byte-checked — ids, references, assets. The preview shows your content coming back out of each candidate, which no platform vendor can show you. Anything that can't cross is named in the report, never dropped silently.
Your content standing up in 2–4 candidate targets, with a written recommendation and a migration plan for each — honest, even when the answer isn't us. The evaluation fee credits in full against the migration.
Your source stays live and is only ever read. Migrations re-run idempotently as content changes, so cutover is a scheduling decision — and a reversible one.
Saved views and listings, menus, URL aliases and redirects, taxonomy trees, moderation states, revision history — the things official migrators quietly drop.
Every route is gated on a check that compares the two ends — your old system and your new one — and a migration ships only when the numbers agree.
| What we check | Estate | Result |
|---|---|---|
| Drupal 7 → Drupal 7 the integrity check: we rebuild your site into the same platform, where any difference at all is a defect rather than a consequence of a different data model | 3,000 nodes 120 terms | node ids, titles, 3,000 body values and their text formats, 3,691 taxonomy references, 1,472 image references, 24 files — identical, 0 references dropped |
| TYPO3 12 → TYPO3 14.3 LTS the upgrade, in one pass instead of six | 83 pages 222 content elements | 82 of 82 page-tree edges, 60 inline items re-owned, body text and all 32 files byte-identical; re-running updates in place rather than duplicating |
| Drupal 7 → TYPO3 14.3 LTS a cross-platform move | content, taxonomy, menus | content items, taxonomy terms and menus all matched end to end; differences that remain are the target's own conventions, and are named |
These are our own test estates, not customer migrations. We have no case studies to show you yet, and inventing them would contradict the only thing we are selling. What we publish instead is the method and the numbers it produces — and your assessment runs the same checks against your estate, so you get this table about your own content before you commit to anything.
Moving a TYPO3 site forward normally means climbing every release in between, and every hop is a chance for an extension to break. We read the old install once and write a current one — the tree, the content elements, the files and their alt text — so the versions in the middle never have to exist.
Verified end to end on TYPO3 12 → 14.3 LTS: the round trip returns identical page, tree and content-element counts, with titles, body text and every file byte-identical. Older sources are read the same way; we confirm your version during the free assessment. Templates and extensions are rebuilt, not carried — that part is a rewrite on any path.
Each stage is small enough to say yes to, and each one pays for itself.
We scan your estate and hand you a map of it: every module bucketed, content counts, real field-mapping verdicts, attention flags. Nobody else gives you this measurement of your own site.
A representative slice of your real content stands up in 2–4 candidates. You get working previews, a written recommendation and a migration plan for each. The fee credits in full against the migration — you never pay twice.
The estate moves to the winner, losslessly — ids, fields, permissions, designs. Your source stays live until cutover day, and cutover is reversible. If you pick something we don't build, we still get you there.
Start free. Pay a small fixed fee to see your content in every candidate — credited in full when you migrate.
Tell us about your estate — platforms, number of sites, timeline. You'll get back a measured map of your own site (modules bucketed, field-mapping verdicts, attention flags) and a fixed quote for the evaluation. No obligation, no sales pressure.
Prefer email? Everything here just reaches a real inbox.