Moving from one page builder to another isn’t a simple export-and-import — each builder stores content in its own format, with its own set of widgets or modules, and some of what exists in the old builder has no direct equivalent in the new one; this check reviews your actual content against the target builder before you commit, so you know precisely what will transfer cleanly and what will need rebuilding. This kind of mismatch is genuinely easy to underestimate from a distance, since a builder’s marketing page always shows its best-case features working smoothly, while your site’s actual accumulated content — years of specific choices made by whoever built each page — is what a real migration has to reckon with directly.
Why we check content, not just count pages
Knowing how many pages you have tells you almost nothing about how much work a switch actually involves, since two sites with the same page count can differ enormously in how much of that content relies on features the new builder simply doesn’t offer.
If you already have a specific new builder in mind, telling us which one lets us check against its actual capabilities rather than a generic comparison.
It’s also worth mentioning any page you consider especially important, such as a landing page tied to active advertising, since those deserve particular scrutiny even if the rest of the site’s content maps across relatively cleanly. A few extra minutes naming these upfront saves real back-and-forth later.
Builder-to-builder content preservation check
Before switching page builders, we confirm exactly what content will and won't carry over cleanly, so nothing is lost partway through the move.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- The builder you’re currently using and the one you’re considering moving to
- The specific pages or the whole site you’d like included in the check
- Any features or layouts you know are especially important to preserve
This or something else?
| You’re considering switching builders and want to know what will transfer cleanly first | This fix covers it |
| You’ve already decided and want the actual migration performed, not just checked | A dedicated conversion service for your specific builder pair |
| You want accumulated data cleaned up in your current builder, not a switch | A builder-specific bloat or cleanup service instead |
| Multiple builders are already active and you want a consolidation plan | Multiple builders active – consolidation plan, a different service |
| You’ve already switched and content is now displaying incorrectly | A different, more urgent repair rather than this pre-check |
What we do
- Catalogue the content, widgets, and layout patterns used across the pages in scope
- Compare each against what the target builder can reproduce natively
- Identify content that will transfer cleanly versus content needing manual rebuilding
- Estimate the realistic scope of a full migration based on these findings
- Flag any features with no equivalent at all, so you can decide how to handle them
- Deliver a written report you can use to plan or commission the actual migration
What is included
- A full content and feature comparison against your intended target builder
- Clear identification of what transfers cleanly versus what needs rebuilding
- Flagging of any feature with no direct equivalent in the new builder
- A written report to plan the actual migration, whenever you’re ready
Not included
- Performing the actual migration itself, which is scoped and quoted separately
- Choosing which builder to switch to, if you haven’t already decided
- Rebuilding content flagged as needing manual work, beyond identifying it
- Ongoing review as your content changes before the eventual migration
Questions about this fix
Do I need to have already chosen a new builder before ordering this?
It helps to have one in mind, since the check is genuinely specific to a builder pair, but we can also help you compare shortlisted options if you're still deciding.
Will this tell me exactly how long the actual migration will take?
It gives a realistic estimate based on what we find, though the final scope is confirmed once the actual migration itself is quoted separately.
What happens to content you flag as having no equivalent?
We describe the closest available alternative so you can decide whether to accept a slightly different approach or handle that content another way entirely.
Is this worth doing if I only have a handful of pages?
Even a small site can have one or two pages built with features that don't translate cleanly, so it's often worth the certainty regardless of overall site size.
Could this check reveal that switching isn't actually worth it?
Yes, and we'll say so plainly if the rebuild required looks disproportionate to the benefit, rather than push you toward a migration that isn't clearly worthwhile.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.