Agency Migration Playbook: Move Client Sites Without Losing Clients

Most Agency Migrations Fail for Relationship Reasons, Not Technical Ones

A 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.

This playbook covers both halves. The technical runbook is complete enough to hand to a developer who has never done a cutover. The client-facing chapters cover what to say before, during, and after, including the conversation nobody wants to have when a migration goes wrong.

Eight Chapters and Seven Ready-to-Use Templates

• Chapter 1: Why Portfolio Migrations Stall
  The five things clients actually judge during a move, and why relationship risk costs more than technical risk.
• Chapter 2: Qualify the First Site
  A weighted scorecard that tells you whether a specific client site is ready to move, ready for discovery, or should wait.
• Chapter 3: Decide the Relationship Model Before the Plan
  Who owns billing, access, support, and the credential of record. Four models, and what each one costs you at renewal and at client departure.
• Chapter 4: The Migration Runbook
  Nine phases from pre-flight through decommission. TTL reduction, staging validation, DNS cutover mechanics, SSL sequencing, email handling, and the failure points named where they actually occur.
• Chapter 5: What a Provider Should Confirm Before You Commit
  Eight scope questions to ask any host, and how agencies who prefer to migrate their own sites use covered migrations as a backstop rather than a handoff.
• Chapter 6: Client Communication Through the Move
  What to say at each stage, what never to promise, and how to charge for migration work when the transfer itself is covered.
• Chapter 7: From One Move to a Portfolio Playbook
  Wave planning: batch size, spacing, scheduling windows to avoid, and which sites never belong in a wave.
• Chapter 8: Three Migrations, Three Plans
  The same framework applied to a brochure site, a WooCommerce store, and a legacy application. One of the three ends in a deferral, and that is the point.

Seven Templates You Can Use Immediately

1. Pre-migration intake form. Everything to document before you touch anything, including the dependencies that break silently.
2. Site qualification scorecard. Seven weighted factors, three decision bands, one automatic disqualifier.
3. Post-migration validation checklist. Eight sections covering rendering, access, functionality, routing, certificates, integrations, email, and monitoring.
4. Rollback decision tree. One page, printable, written so someone can follow it at 2 a.m. without calling you.
5. Client communication templates. Kickoff, cutover, completion, incident disclosure, and deferral recommendation.
6. Completion report and sign-off sheet. What was moved, what remains, where support routes, and when the old environment retires.
7. 15-minute portfolio self-assessment. Nine questions that tell you whether the next step is scheduling or discovery.

This Playbook Is Written for You If

• You manage client hosting across two or three providers because that is how the accounts arrived, not because anyone chose it.
• You have a client site you know should move, and you have been putting it off because a bad week outweighs a better server.
• You lost a weekend to a transfer that should have taken two hours, and you still are not sure which step caused it.
• You have been asked to quote a migration and do not know whether to bill four hours or fourteen.
• You want to consolidate the portfolio and cannot make the case to a client whose site is working fine today.