Shift

Migrating to Cyberfusion

"I want truly managed hosting, but I'm already swamped."

No worries: Shift is our migration method, shaped by 10+ years of moving sites and applications of every size. We take at least 70% of the work off your plate, and before you know it, everything runs at Cyberfusion.

We migrate from

Not sure if Core fits? See how Core compares →

Hosting type

Shared hosting Outgrown it, or looking for more stability and performance?
Self-managed VPS Looking to hand off more of the work without giving up the freedom?
Cloud tooling Deployment is easy, what comes after gets complicated. You need truly managed hosting, with the same freedom.

Control panel

Provider

What are you migrating?

Pick your situation. We'll take it from there.

Where does the time go?

A typical Shift migration, broken down by who does what.

10%

Timeline for a full portfolio migration

Migrating everything at once? Here's what to expect.

Tomorrow

Conversation and quote

We discuss your setup, the number of projects, and anything special. You receive a quote soon after.

2 weeks later

Quote approved

You approve the quote and we get to work.

1 day later

Server ready

Your server is provisioned. Time to inform your clients about the upcoming migration.

Every week

Batch migration

We migrate a batch of sites. You run the checks. Dates and times agreed in advance.

After ~4 weeks

Migration complete

All sites are live on Core. Time to celebrate.

Tips for a smooth migration

Preparation

Own it like a project.

Migrations that go sideways usually lack one thing: clear ownership. Assign a project owner for decisions and planning, a technical lead for the checks, an operations manager for contracts, DNS, and notice periods, and a client contact for communication. Smaller team? One person can wear multiple hats - just make sure every hat has a name on it.

Sort out DNS first.

Who controls your DNS? Where do the records live? Do you have the credentials, or does a former colleague? It sounds trivial until you're staring at a login screen at 11 PM with nobody who knows the password. DNS access is the first thing we ask about for a reason.

Keep the old environment around a while.

Everything migrated? Don't cancel the old environment right away. If something does come up later, we still have access to the old configuration and data.

Know exactly what you're migrating.

Which applications are live? What external dependencies exist? How are cronjobs, firewall rules, and caching configured? What has accumulated over the years that nobody documented? The more complete the picture upfront, the fewer surprises during the migration.

One thing at a time.

Resist the urge to combine a migration with major application updates. Each is complex enough on its own. The exception: database versions like MariaDB sometimes require an upgrade as part of the migration, but version differences are typically minor and rarely cause issues. Everything else can wait until you've landed.

Telling your clients

The invisible migration.

Schedule migrations outside peak hours, test thoroughly before any DNS change, coordinate tightly with everyone involved. When it's done right, the only thing your clients should notice is that their site got faster.

Questions are coming. Be ready.

Why the switch? Will there be downtime? What changes? Have a short, honest answer for each. It should match existing agreements and contracts. People don't need you to justify the decision - they need to understand it.

Two or three updates. No more, no less.

Start communicating well before the technical work begins. Two to three updates is usually the right balance - enough to keep people informed, not so many that they stop reading.

Give clients time to act.

Some clients have to do things on their end - update DNS, change settings, brief their team. Tell them what's needed and give them the time. Surprise migrations don't make friends; good, timely communication does. Better still: it strengthens client relationships.

It's an upgrade, not a disruption.

Faster load times, stronger security, features that weren't there before - that's the story. Tell your clients. A migration presented as an investment, rather than a hassle, is also a logical moment to revisit your terms and pricing.

Want to let your customers understand the advantages? Share our hosted-by page →

Get started

Pick what suits you best.

Transfer 1 site for free

Tell us what to migrate and we'll get started.

William
William David EdwardsDevOps Engineer

I personally oversee every Shift migration.

  • We handle at least 70% of the work
  • Tested before DNS switch
  • No commitment

Ask a question

About migration, timing, complexity. Anything.

William
William David EdwardsDevOps Engineer

I read every question and reply within one working day.

  • Direct reply from an engineer
  • No commitment
Migratol

Need a little migration courage?

We developed Migratol - clinically unproven relief for migration anxiety. Side effects include improved uptime, faster load times, and the sudden urge to migrate all your other sites too.

Fill in your address and we'll send you a box.

William David Edwards

Got a question? Email or call William.

William David Edwards · founder

See more contact options →