How Agencies Can Move Client Websites Without Moving Everything at Once
Portfolio migrations fail for relationship reasons more often than technical ones. This guide covers the decisions an agency makes before any transfer begins: which client site should move first, who should own the hosting account, and when consolidation is worth the risk to a working relationship.
A hosting migration looks simple from the outside. Copy the files, move the database, update DNS, confirm the site loads. For an agency, that is roughly half the work.
The harder half is protecting the client relationship while changing something the client may not understand but will notice immediately if it breaks. You are managing access, expectations, billing, support ownership, maintenance windows, and the reputation your agency built on being the team that keeps the website working.
So the safest portfolio migration starts with one well-chosen site, one clear operating model, and one result you can evaluate before repeating it.
What Clients Actually Judge During a Migration
Almost no client evaluates a migration by the elegance of the transfer method. They evaluate five things:
- The site stayed available.
- Forms still deliver.
- Email still works.
- Stakeholders knew what was happening.
- Someone took ownership when a question came up.
Agencies carry two kinds of risk against that list.
- Technical risk is the chance that a file, database, certificate, integration, or routing change behaves differently in the new environment.
- Relationship risk is the chance that unclear ownership turns a manageable issue into what feels like an agency failure.
The second one does more damage, because it changes how the client sees your team. A technically clean move can still feel chaotic when nobody knows who is watching the cutover, which team supports email, or where the client should report a problem.
Before choosing tools or booking a window, answer four questions in writing:
- Why are we moving this client now?
- What outcome should improve after the move?
- Who owns each part of the client experience during and after the migration?
- What evidence will tell us this relationship should expand to another site?
If those answers are vague, the migration is not ready, even when the backup file is.
Choose a First Site You Can Fully Control
The most valuable or most complex client feels like the obvious place to prove a new hosting partner. It is usually the worst place to learn a new workflow.
A useful first migration is representative enough to teach you something and contained enough that your team can investigate surprises without a crisis. Look for a stable site your team understands, with clear ownership, working administrative access, a current backup, and a client who can approve a defined change window.
What Makes a Strong First Candidate
- Runs a common CMS or a familiar application stack.
- Has limited real-time writes, transactions, or membership activity during the proposed window.
- Has documented ownership of DNS, domain, email, analytics, and third-party services.
- Represents a workload you expect to see again elsewhere in the portfolio.
- Has a client relationship strong enough to support honest testing and sign-off.
What Makes a Weak First Candidate
- Your highest-revenue client or most business-critical application.
- A site with undocumented custom code, abandoned plugins, or unknown server dependencies.
- An ecommerce or membership site with constant writes and no agreed maintenance approach.
- A project where the domain, DNS, email, or hosting account sits with a former vendor.
- A site being rushed because the current hosting account expires tomorrow.
That last one deserves emphasis. Expiring-account urgency is the most common cause of bad agency migrations, because it removes your ability to test, to run environments in parallel, and to roll back. If a client account expires in 72 hours, the right first move is usually to renew for one more term and migrate on a schedule you control.
Better sequencing: start with a low-to-moderate-risk site that resembles future work. Learn the process there, then move toward higher-value or more complex workloads with evidence behind you.
Decide the Relationship Model Before the Hosting Plan
Agencies tend to jump straight to product selection: shared, WordPress, reseller, VPS, or dedicated. The more consequential decision comes first. Who owns the account, the billing, the access, the support relationship, and the day-to-day client experience?
That answer determines what your agency can standardize, where margin comes from, and how support feels to the client. Several models can coexist inside one portfolio.
A small client may be happiest owning a straightforward plan and granting your team access. Another may expect hosting to be part of the retainer. A high-resource application may need an environment your agency configures directly. Do not force all three into one account structure because consolidation sounds efficient.
Once the relationship model is settled, compare hosting options against the workload itself: application compatibility, CPU and memory, management level, security requirements, expected growth, and the responsibilities your agency is prepared to own. The Agency Hosting Solutions page maps those models to specific plans, and the hosting decision matrix in The Digital Marketing Agency’s Complete Guide to Strategic Hosting works through the same comparison by client scenario, budget, and agency size.
Run the First Move as a Pilot
A pilot creates a decision point. A promise creates pressure to keep going even when the evidence says the approach needs to change.
Keep the first move small enough that the agency, the client, and the hosting team can agree on scope. Technical details vary by workload. The decision structure does not qualify the site and the destination, move and test and cut over with named owners, then validate the client experience and record what you learned before selecting the next site.
That third step is where most agencies lose the compounding benefit. A migration nobody reviewed teaches you nothing you can hand to a junior team member.
How the Migration Guarantee Supports Agencies Who Migrate Their Own Sites
Plenty of agencies prefer to run migrations in-house. You know the stack, you control the window, you own the client narrative, and in many shops the migration is billable work. Handing that to a vendor can feel like giving up the part of the process you are best at.
That is why the free migration benefit in the Agency Partner Program is better understood as coverage than as a handoff. Free site migrations are included at every partner tier, so the option stays available whether you use it on the first site, the fiftieth, or only on the one that goes sideways at 11 p.m. on a Thursday.
Three ways agencies who migrate their own sites use that coverage:
- Offload the repetitive ones. Brochure sites, small WordPress builds, and straightforward cPanel accounts move fine without senior developer hours. Send those to the transfer team and keep your engineers on billable client work.
- Keep a backstop mid-migration. Panel-to-panel transfers, oversized databases, and legacy PHP environments are where in-house migrations usually stall. Coverage means escalating is a scope decision, not a budget conversation with the client.
- Split the work. Your team handles the application, theme, and build validation. The transfer team handles the server-side move. You keep DNS timing, which keeps the cutover on your schedule and your client’s.
Website files, databases, and applications are the core of a standard transfer. Email, DNS, SSL, and custom server configuration are separate scope items to confirm per site rather than assume. New complex builds can also draw on Launch Assist, which includes two hours of managed migration support from the InMotion Solutions team on all plans.
Questions Worth Asking Your Hosting Partner First
A useful migration conversation replaces broad promises with defined scope. Before you present a plan to the client, ask the provider to confirm:
- What is not included? Source environment, destination plan, access, and complexity all shape the actual path. A provider unwilling to name the exclusions is describing marketing rather than scope.
- Is email part of this? Mailbox data frequently sits outside a website transfer. Assuming otherwise is how client email goes down on cutover day.
- Who validates, and what is the rollback? If nobody can tell you the sign-off point or how long the prior environment stays available, you do not have a plan.
The playbook covers all eight scope questions, including the ones about access requirements, timing variables, and where cost shifts from included to priority service.
Client Communication is Part of the Migration
Your agency should own the client narrative even when another team performs most of the technical transfer. Clients want confidence that someone understands the plan. They do not want a stream of low-level status messages.
Before the window, explain why the move is happening, what should improve, what stays the same, and how to report a problem. Avoid promising the client will notice nothing. Promise that your agency has a plan, named owners, testing criteria, and an escalation path. The first promise can be broken by a DNS resolver you do not control. The second is entirely within your power to keep.
At cutover, send one update stated in business terms with a next-update time. After validation, close the loop with what was checked, what remains, where support requests go, and when the old environment retires.
The harder conversations are the ones most agencies have not scripted: disclosing an incident before the client notices it, and recommending that a migration should wait. The playbook includes five ready-to-send templates covering both.
The Business Case for Thoughtful Consolidation
Agencies rarely lose margin because one hosting invoice runs five dollars high. They lose it through scattered logins, inconsistent renewal dates, unclear support ownership, one-off environments, and senior staff spending hours reconstructing how a client site was built.
A well-designed hosting portfolio reduces that drag. Fewer management patterns make onboarding, access, documentation, support, and renewal planning easier to teach to a junior team member. A clearer client-facing service model also gives your agency a stronger foundation for packaging hosting, maintenance, and performance work into recurring revenue. Pricing that service line is its own exercise, and the packaging and reseller-versus-retail chapters of The Digital Marketing Agency’s Complete Guide to Strategic Hosting cover the structures agencies actually use.
Consolidation still has to earn its place. If a site is stable, profitable, documented, and well supported, moving it only to raise a site count adds risk without a client outcome. Prioritize the sites where a new relationship solves a real problem: poor support, operational sprawl, limited access, thin performance headroom, ownership mismatch, or a hosting model that no longer fits the workload.
Three Questions Before You Schedule Anything
If any answer is unknown, the next step is discovery rather than scheduling.
- Can you name the business reason for moving this site now, in terms a client would accept?
- Do you know who holds the hosting account, domain, DNS, and email access, and can you reach all four today?
- Have you restored this site’s backup successfully at least once?
That third one catches more problems than the other two combined. A backup nobody has restored is a hypothesis.
For a scored answer rather than a gut check, the playbook includes a weighted scorecard across seven factors with three decision bands, so a specific client site comes back as go, discovery first, or defer.
Common Questions About Agency Client Migrations
Should the Agency or the Client Own the Hosting Account?
It depends on how you want to bill and support. Client-owned accounts keep renewals and support with the client and transfer cleanly if the relationship ends. Agency-owned accounts give you pricing control and a recurring revenue line, and they make you first-line support by default. Decide before the migration, not after.
When Should an Agency Decide Not to Migrate a Client Site?
When the site is stable, documented, profitable, and well supported where it is. Moving it raises your site count without solving a client problem. Also defer when access is incomplete, when the current account expires within days, or when nobody can confirm what the site depends on.
Do Free Migrations Mean My Agency Cannot Charge for Migration Work?
No. A covered transfer moves files and databases. It does not cover discovery, dependency mapping, staging validation, client communication, post-migration QA, or DNS coordination. That work is yours and it is billable. Agencies commonly price it as a fixed-fee project by complexity band or fold it into a new-client onboarding fee.
How Do I Know If a Client Site Is Ready to Migrate?
Ready means four things are true: you have full administrative and DNS access, a backup you have actually restored, a documented list of integrations and scheduled tasks, and a client who has approved a window. Missing any one of those turns a scheduling decision into a discovery task.
How InMotion Hosting Supports Agency Migrations
Bring InMotion into the conversation before you commit to a migration method or a client date. The team can compare hosting options against the workload, review the available migration path, and tell you what information the first qualified site requires.
Partners get free site migrations at every tier, WebPro for managing client accounts from one login, and access to InMotion Solutions consulting hours for custom client environments at higher tiers. Support is handled by in-house teams who complete more than 280 hours of training before taking Tier 1 tickets, with average support tenure above five years. The infrastructure underneath is owned and operated by InMotion across its own data centers, which is why capacity and configuration questions get an answer rather than a ticket to a third-party cloud provider.
Every plan is covered by a 90-day money-back guarantee, which gives a first client migration a defined evaluation period rather than an open-ended commitment.
Start With One Site You Know Well
A portfolio migration should not be a leap. It should be a sequence of qualified decisions, each supported by evidence from the move before it. Choose one representative site, clarify who owns what, confirm the destination and scope, communicate the plan, validate the result. Then decide whether the next site follows.
That gives your agency something more durable than a one-time transfer: a hosting relationship and an operating model you can expand on purpose.
Apply for Free Migrations and Partner Pricing: Join the Agency Partner Program
Free Download: The Agency Migration Playbook
The step-by-step companion to this guide. Includes the nine-phase migration runbook from pre-flight inventory through decommission, a weighted site qualification scorecard, a one-page rollback decision tree, five client communication templates, and three worked migration case studies.
Additional Guides & Tools
Blog
Stay updated with the latest web hosting news, tips, and trends. Explore our expert articles to enhance your online presence and keep your website performing at its best.
Support Center
Get 24/7 assistance from our dedicated support team. Access a wealth of resources, tutorials, and guides to solve any hosting issues quickly and efficiently.
Managed Hosting
Experience high-performance, secure, and reliable managed hosting solutions. Let our experts handle the technical details while you focus on growing your business.