We assist with migrating your site to a new host by working through your control panel — setting up the new environment, transferring files and database, and coordinating the cutover — and how much of this we can handle depends on what access and tools your specific new and old hosts’ control panels actually provide.
Host migration assistance via control panel
A host migration coordinated through both control panels — flagged early if a feature won't carry over.
- 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
- Access to both your current and new hosting control panels
- Confirmation of your preferred cutover timing, ideally during lower-traffic hours
- Confirmation of what’s included in your new hosting plan, so we know what’s actually available to configure there
This or something else?
| You want assistance migrating your site to a new host using both control panels | This fix covers it |
| You want a more comprehensive, code-level migration, not primarily a control-panel-driven one | Host-to-host migration – single site, in the Backups, Staging & Migration Ops category, the more technical version |
| You’re just changing DNS or nameservers, not actually moving hosting | Registrar-level DNS & nameserver changes, or Cloudflare DNS migration from registrar |
| Your new host’s control panel doesn’t support a specific feature your current setup relies on | We’ll identify this early and flag it plainly, since that’s a genuine limitation of the new environment, not something we can configure around |
What we do
- Review both control panels to understand available tools and any limitations
- Prepare the new hosting environment to match required settings
- Transfer files and database using available control panel tools where possible
- Test the site thoroughly on the new host before any DNS change
- Coordinate DNS cutover at your agreed time
- Verify the live site functions fully on the new host after cutover
What is included
- A migration to your new host coordinated through available control panel tools
- Thorough testing before cutover
- DNS cutover managed at your agreed time
- Post-cutover verification
Not included
- Recreating a feature your new hosting plan simply doesn’t offer, if your current setup depends on something specific to your old host — we’ll flag this clearly during planning, not discover it mid-migration
- Purchasing or setting up the new hosting account itself, unless already arranged
- Resolving pre-existing site issues unrelated to the migration itself
- Ongoing management of either hosting account after migration
Questions about this fix
What if my new host doesn't offer a feature my site currently relies on?
We'd identify this during initial review of both control panels, before starting the actual migration, so it's a known consideration you can address (finding an alternative, or reconsidering the new host) rather than a surprise discovered partway through.
Given this relies on control panel tools specifically, is downtime more likely than a fully custom migration?
Not inherently — we still test thoroughly on the new host before any DNS change regardless of which tools are doing the transfer, so the same careful-planning discipline applies whether the migration leans on control panel features or more custom, code-level work.
Is this different from the more technical host-to-host migration fix?
This one works primarily through both hosts' control panels and their available tools; the more technical version is suited to situations needing deeper, code-level intervention beyond what control panel tools alone can handle.
What happens to my old hosting account after migration?
We'd recommend keeping it active and unchanged for a period after cutover, as a safety net, until you're fully confident the new host is working correctly.
How long does a typical control-panel-driven migration take?
It varies with site size and what each control panel's tools support — we'd give you a realistic timeframe once we've reviewed both environments.
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.