Moving over 100 sites to a new host sounds like the kind of job that ends in a long night, a spreadsheet full of broken links and an inbox full of angry clients. That is why cPanel migration for agencies has a reputation that puts people off making the move at all. Most agency owners we speak to are not happy with their current host. They stay because the risk of moving feels bigger than the pain of staying.
We recently completed a migration of 145 websites for a new agency customer. Everything came across from their old cPanel-based provider: website files, databases, email accounts and hosting configurations. The work was scheduled around their calendar, not ours, and the sites stayed online throughout. No downtime, no emergency calls, no clients ringing to ask why their site had vanished.
This post walks through how that migration actually worked. It is not a sales pitch dressed up as a case study. It is a practical look at what gets moved, what can go wrong, what we check, and what an agency should ask any host before handing over hundreds of client sites.
Why cPanel migration for agencies feels risky
The fear is rational. When you run one website, a migration is a small piece of work with a small blast radius. When you run 100+ client websites, every one of those sites belongs to someone who will notice if it breaks, and who will phone you rather than the hosting company.
Agencies also carry a specific type of risk that individual site owners do not. Your client does not care which host you use. They care that their contact form works, their email arrives and their site loads. If any of those break during a move they made no decision about, the damage lands on your relationship, not your host’s.
There is a second problem. Most agency hosting has grown organically over years. Sites were added one at a time, often by different people, often with slightly different setups. Nobody has a full inventory. That uncertainty is what makes an agency hosting migration feel dangerous, because you cannot confidently move what you have not fully mapped.
The answer is not bravery. It is preparation. A no downtime website migration is mostly planning work, with the actual switch being the smallest and least dramatic part of the job.
What we moved for this agency
The agency came to us running 145 client websites on a cPanel-based provider. A typical mix: WordPress sites of varying ages, a handful of static brochure sites, several sites with custom code, and a long tail of small sites that had been quietly running for years without anyone touching them.
Here is what came across:
- Website files. Every file for every site, including uploads, themes, plugins, custom code and the odd forgotten directory that turned out to be doing something important.
- Databases. Full database exports and imports, with connection details updated so each site pointed at the right place on the new platform.
- Email accounts. Mailboxes with their existing mail, plus forwarders and aliases. Email migration is where most agency moves go wrong, so it gets the most attention.
- Hosting configurations. PHP versions, redirects, SSL certificates, cron jobs, custom rules and the small per-site settings that only reveal themselves when they are missing.
The unglamorous part is the inventory. Before anything moved, we built a complete picture of what existed: how many sites, what each one ran on, which had email attached, which had non-standard configurations and which had dependencies nobody had documented. cPanel’s own backup documentation shows how much can sit inside a single hosting account, and that complexity multiplies across an agency estate. That list is what turns a risky move into a routine one.
Why timing matters for agency migrations
We scheduled this migration around the agency’s needs. That sounds like a small courtesy. In practice it is one of the things that decides whether a migration is calm or chaotic.
Agencies have rhythms. There are client launch weeks, campaign periods, invoicing runs and quiet spells. A migration that happens during a quiet spell has room to breathe. If something needs a second look, there is time to give it a second look. A migration that happens the week before three client launches has no slack in it at all, and no slack is where mistakes get made.
Timing also matters for the people involved. Someone on the agency side needs to be reachable to answer questions, confirm which sites are live and flag anything unusual. That person should not be answering those questions at two in the morning while also managing a client crisis.
We ask agencies three questions before agreeing a schedule:
- When is your quietest period over the next few weeks?
- Which client sites have the lowest tolerance for any disruption at all?
- Who on your side is the point of contact, and when are they actually available?
The answers shape the plan. Sometimes that means a weekend. Sometimes it means a Tuesday afternoon, because that is genuinely the calmest window the agency has.
How no downtime migrations work in practice
A no downtime website migration works because the old site keeps serving traffic while the new one is being built and checked. Nothing gets switched off in the hope that something else comes back on.
The sequence looks like this:
- Inventory and audit. Map every site, database, mailbox and configuration on the old cPanel account. Identify anything unusual before it becomes a surprise.
- Build on the new platform. Create the accounts, copy files and import databases while the live sites carry on as normal. At this point nothing is user-facing.
- Test against the new platform. Load each site on the new server before any DNS changes, so problems are found while the old site is still happily serving visitors.
- Sync email and lower TTLs. Move mailboxes across and reduce DNS TTLs in advance so the eventual switch propagates in minutes rather than hours.
- Final sync and cutover. Copy anything that changed since the initial copy, then update DNS. Both platforms are serving during propagation, so visitors reach a working site either way.
- Post-migration checks. Confirm SSL, forms, email flow, redirects and admin logins across the estate, then decommission the old hosting once everyone is satisfied.
The critical detail is step five. During DNS propagation, some visitors hit the old server and some hit the new one. If both are working, nobody notices anything. If you have switched the old one off, some visitors get nothing. That single decision is most of the difference between a smooth move and a support nightmare. We covered our own move away from cPanel in why we left cPanel and what we chose instead, and the same principles applied there.
What changed after the move
The point of a migration is not to end up where you started on different hardware. Three things changed for this agency.
The sites are faster. Modern server stacks, current PHP versions and sensible caching make a measurable difference, particularly for older WordPress sites that had been sitting on ageing infrastructure for years. Clients notice speed even when they cannot explain it.
They have geo-diverse hosting. Sites can be placed on servers in the region that suits the audience rather than everything landing wherever the old provider happened to put it. For an agency with clients in different markets, that is a practical advantage rather than a technical footnote. We wrote about how this works in multi-region hosting with UK and USA servers.
They manage everything from one clean panel. No more logging into separate accounts to find one client’s database. One interface, one place to see the whole estate, one place to add a new site.
None of these are dramatic on their own. Together they change how much time the agency spends on hosting admin every week, which is time they can bill instead.
What agencies should check before leaving cPanel hosting
Whether you move to us or somewhere else, these are the areas that decide whether a migration goes well. Work through them before you commit to a date.
| Migration area | What can go wrong | What needs checking |
|---|---|---|
| Website files | Missing uploads, or theme and plugin files left behind | File counts match, permissions are correct, every site loads on the new server |
| Databases | Broken connections, or an import that captured stale data | Database imports complete, config files updated, forms and logins tested |
| Lost mail, missing forwarders, confused clients | Mailboxes and mail history, forwarders and aliases, MX and DNS records | |
| DNS and configs | Slow propagation, SSL warnings, redirects that stop working | TTLs lowered in advance, records confirmed, SSL issued, redirects tested |
Two additions worth making to that list. First, find out who controls the DNS for each client domain. On an estate of 100+ sites, some domains will sit in registrar accounts the agency does not have access to, and discovering that on migration day is painful.
Second, ask what happens if something breaks. Not whether it might, but who fixes it, how quickly and at what cost. A host that answers that question clearly is a host that has done this before. Our website rescue hosting post covers the sort of problems that surface when nobody asked that question early enough.
When old cPanel hosting starts holding agencies back
Plenty of agencies run on cPanel without much trouble. The friction tends to appear as the number of sites grows, and it usually shows up in the same ways.
- Admin time creeps up. Small tasks that take two minutes per site take three hours across an estate of 100+.
- Client access is awkward. Giving a client limited access to their own site means either handing over too much or handling every request yourself.
- Costs stop making sense. Reseller pricing that worked at 20 sites often looks less attractive at 100+, particularly once you factor in the time cost of managing it.
- The platform ages. Older PHP versions, dated interfaces and licensing changes you did not choose and cannot influence.
- Support gets thinner. Generic responses to specific problems, which is fine for a hobby site and much less fine when a client’s booking form is down.
If two or three of those sound familiar, the calculation has probably already shifted. The cost of staying is being paid in hours rather than pounds, which makes it easy to miss. Our guide to cPanel to Enhance platform migration goes into the technical detail of what actually differs between the two.
Why a single clean panel matters when managing many sites
This is the part agencies underestimate until they experience it. Managing 100+ sites through separate logins and a cluttered interface is not just slower. It changes what you are willing to do.
When a task is fiddly, it gets postponed. Updates get delayed, backups go unchecked, staging sites never get created because setting one up is a chore. The interface quietly shapes the standard of care across the whole estate.
A single panel changes that. Everything in one view. Add a site in under a minute. Give a client scoped access to their own site without exposing anything else. Spin up staging without ceremony. Check backups across the estate without visiting 100+ pages.
The result is that maintenance actually happens, because doing it properly no longer costs an afternoon. If you want to see how the interface works before committing to anything, our guide to the Enhance control panel walks through it, and our reseller hosting pages cover how agencies typically set things up.
Final Thoughts
Migrating 100+ sites without downtime is not a trick. It is an inventory, a plan, a sensible schedule and a cutover that never turns anything off before the replacement is proven to work. The work is mostly done before the day itself, which is exactly why it ends up being uneventful.
The agency in this case study now has faster sites, hosting spread across regions that suit their clients, and one panel to run the lot from. What they mainly gained was the absence of a problem: no client noticed the move, which is the highest compliment a migration can receive.
If you are managing multiple client websites on old cPanel hosting and the thought of moving is what keeps you there, it is worth having a conversation about what a planned migration would actually involve. We will look at your estate, tell you honestly what is straightforward and what needs care, and give you a schedule that fits around your work rather than disrupting it. No obligation to go ahead, and no pressure if the timing is not right yet.
