Moving without a rebuild
Replatforming is the part nobody plans for. Here is what actually happens, in the order it happens.
The four steps
No durations here. We don't publish timings we can't hold — the assessment gives you dates for your own estate.
-
1
Assessment
We take stock of your existing content and structure, and you get back a list: what transfers automatically, what has to be done by hand, and what we deliberately leave behind. Nothing moves until you've approved that list.
-
2
Import
Your content appears in the Central Admin, not yet public. Nothing is required from you at this stage. When it's done, your editors can log in and look around.
-
3
Running in parallel
The old system stays live while the new one is finished. Your editors work in the new one; visitors still see the old one. This is where content decisions get made, with both versions in front of you.
-
4
Cutover
DNS change, redirects go live, old URLs keep working. You choose the date. The old system can be switched off afterwards — it doesn't have to be.
What comes across automatically
If you're on WordPress, most of it. We've built the tooling for that path: content types, media, menu structure and metadata transfer with a field-level mapping you approve before anything moves.
From anything else, the honest answer is that it depends on what's underneath. The assessment step exists to find that out and tell you, rather than to discover it halfway through.
What we do by hand
Whatever doesn't map cleanly. Content that lives in a plugin's own tables, page layouts assembled from a builder that has no equivalent, taxonomies that describe something other than the content.
These are identified in the assessment and quoted separately, so a migration doesn't turn into an open-ended cost.
What we don't bring
Not everything in an old system deserves to survive the move. Pages nobody has opened in three years. Four versions of the same PDF. Taxonomies that describe an organisation chart from two restructures ago.
We list these before the import, and you decide. What we won't do is move them silently so the new system looks full on day one — that is how a migration becomes a rebuild two years later.
The old content remains in your export until you tell us to discard it.
URLs and search
Every existing URL either continues to work or redirects to its replacement, permanently. The redirect map is part of the assessment, not something improvised at cutover.
Canonical links, language relationships, sitemap and immediate indexing are platform capabilities, not migration tasks — so search position is carried across rather than rebuilt.