Website migration as a service: how an agency can win clients stuck on old sites

By Ranjit Bhinge, founder of Blur Studio · Updated · 9 min read

Short answer: Website migration as a service means you move a client's site from an old platform to a new one and protect their search traffic while you do it. It is a good offer because the client already has a problem (a slow, hacked or hard-to-edit site) and a fear (losing their Google traffic). Sell it as a fixed-scope project with four steps: audit, redirect map, move, and check. Price it by the number of pages and the amount of work that cannot be automated, not by hours.

Ranjit Bhinge

You keep meeting business owners who know their site is stuck, and who are afraid that moving it will cost them their Google traffic.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

The offer in one line: "We move your site to a platform you can edit, and we keep your search traffic safe while we do it." To deliver it you need a fixed process, a redirect map (a list that sends each old web address to its new one), a clear price per scope level, and an honest view of what each platform allows. This guide gives you all four, and shows where a tool such as Ploy (an AI platform that rebuilds and hosts sites) can speed up the rebuild, and where it cannot.

This page may contain affiliate links from which Blur Studio earns commissions.

This is for agencies of 10 to 30 people. It covers who needs to move, how to find them, the four-step process, what each old platform lets you take out, a price and scope guide with made-up numbers, contract points, and a first-week plan. For the full SEO checklist, see how to keep SEO rankings when you rebuild or move a client site. For what clients pay, see how much a website migration costs.

Who needs to move, and why

Clients rarely ask for a migration. They ask for something else. Listen for these:

  • "Our site is slow." Old themes and heavy plugins (add-on software for a website) slow a site.
  • "We got hacked." Patchstack, a company that sells WordPress security protection, counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 91 percent in plugins. That is one vendor's count, but it shows why old plugin-heavy sites are a risk. See moving off WordPress when it is slow, hacked or hard to edit.
  • "I cannot change anything without calling someone." The site is hard for staff to edit.
  • "The person who built it is gone." Nobody has the logins.
  • "Our plan keeps going up." A builder changed its prices. Webflow, a hosted site builder, changed its plan structure in 2026.
  • "We are rebranding." A natural moment to move.

Where to find them: your own client list, past proposals that stalled, local business groups, and a free "site health" check you do on a prospect's public pages (speed, mobile layout, forms working, security warnings). Offer the check, not a sales pitch.

What each old platform lets you take out

This is the part clients do not know and you must. The limits come from each vendor's own pages as of November 2026.

Old platformWhat you can take outWhat you cannot
WordPress (self-hosted)Content, files and database are under the hosting account holder's controlPlugins and theme features do not carry over; forms and shortcodes need rebuilding
WixMedia, and a domain you can point elsewhereWix's help center says the site must run on Wix's servers, so there is no export to another host
SquarespaceAn XML file for WordPress only, with limited page typesMany page types, product blocks, video blocks, drafts and custom CSS
WebflowExported HTML, CSS and JavaScript on a paid Workspace planCMS (the content database), forms and ecommerce; the export cannot be re-imported
FramerAssets and redirect listsFramer says it offers no HTML export for self-hosting

The point for your pitch: on Wix, Framer and much of Squarespace, a migration is a rebuild, not a transfer. That is also your reason for a fixed fee: the work is design and content decisions, not file copying. Our guides on leaving Wix or Squarespace and leaving Webflow or Framer go deeper on each.

The four steps

Step 1: Audit

Record what exists before you touch anything. Without this you cannot prove you did no harm.

  1. Export every URL on the old site with a crawler (software that follows links and lists pages, such as Screaming Frog) and from the sitemap (the XML file that lists a site's pages).
  2. Pull 12 months of organic clicks per page from Google Search Console (Google's free tool that shows how a site appears in search), and the top pages from analytics.
  3. List what is not a page: forms, tracking tags, booking widgets, payment links, email sign-up, cookie banners.
  4. Note who owns the domain, hosting, analytics and Search Console. Get logins in the client's name before you start.
  5. Sort pages into three groups: keep as is, improve, retire.

Step 2: Redirect map

A redirect map is a two-column sheet: the old URL, and the new URL that replaces it. A 301 redirect is the permanent kind of forwarding that tells Google the page moved. Google's own site-move guide says to prepare a mapping from current URLs to new ones, to set up server-side permanent redirects, and says 301 redirects do not cause a loss in PageRank (Google's link-strength measure). Keep URLs the same wherever you can, because every changed URL is something to map and test.

Check each platform's limits. Wix's help center says a redirect CSV file can hold at most 500 redirects at a time. Squarespace's move guide says to record old URLs in a spreadsheet and set 301 redirects where new URLs differ. Ploy's migration docs say to keep URLs the same where you can and to add 301s in its Path routing for any that change.

Step 3: Move

Build the new site on a staging copy (a private test version) that Google cannot index. Keep titles, descriptions, headings and body text for pages that rank. Rebuild forms and tracking, then test them. Do not launch on a Friday.

Where an AI tool helps: Ploy's Agent works like this. Ploy says you paste a public URL into the Agent, it inventories the site, shows a plan, rebuilds the pages on a design system (a shared set of colors, fonts and components) and imports posts into its database. Its WordPress migration docs say it is a rebuild, not an identical copy, so review every page, and that nothing changes live until you approve. Large sites can move key pages first while the old site serves the rest. Forms, plugins, shortcodes, embeds, custom code and private pages may need separate work. Migration uses AI credits, and larger sites use more. One customer story on Ploy's site describes about 600 WordPress pages moved over a few evening sessions in about a week, which is the company's own account with no search results given. Use it as a sign of speed, not proof of results.

Step 4: Check

After launch, compare against the audit. Submit the new sitemap in Search Console, spot-check 50 old URLs to confirm each redirects to the right page in one hop, and watch clicks per page for the next 8 weeks. Google says that for medium-sized sites it can take a few weeks or more for new URLs to replace old ones in results. Expect some movement and report it to the client before it happens.

What to promise, and what not to

Do not promise rankings, traffic or a recovery date. Studies of domain moves, which are riskier than a platform change on the same domain, show wide ranges. A Search Engine Journal study of 892 domain migrations found an average of 523 days for the new domain to match the old one's estimated traffic, and SALT.agency reported a median of 304 days across 1,052. No dataset covers same-domain platform switches, so say that plainly. What you can promise is a process: a full URL inventory, a redirect map, testing, and monitoring. For the domain-change case, Google's Change of Address tool says to keep redirects in place for at least 180 days and to keep paying for the old domain for at least a year.

Price and scope guide

Seller prices vary hugely. Goodspeed, a Framer-focused agency, says its migrations start from $10,000 with about 5 weeks and 30 days of monitoring, and says very low quotes usually cover a content transfer, not a rebuild with redirects, SEO checks and monitoring. Other seller listings run from about $1,500 to $35,000. Those are sellers' figures, and none is a market average. Price by scope.

Worked example (made-up numbers, replace with your own).

ScopeWhat it coversExample fixed price
LightUp to 15 pages, same URLs, forms and tracking rebuilt, redirect check, 2 weeks of monitoring$3,500
StandardUp to 60 pages, some URL changes with a redirect map, content cleanup, staging, 6 weeks of monitoring$9,000
ComplexOver 60 pages, ecommerce or bookings, custom code, multi-language, 8 weeks of monitoringQuote after a paid audit

Charge for the audit separately, for example $750 that is credited to the project if the client goes ahead. It filters out tire-kickers and tells you what the real scope is. Add a line for the new platform's subscription so the client knows the running cost. On a hosted builder, ask the client to hold the plan in their own name. See how to price website builds when AI cuts the hours.

What drives price up: more pages, ecommerce, forms and integrations, content rewrites, more than one language, changed URL structures, and clients who are slow to send logins and content. Put a change process in the contract so extra work gets a new quote.

Contract points for a migration

  • The domain and hosting accounts are in the client's name. Get the logins before the project starts.
  • A page count and a list of what is not included, such as new content and ecommerce.
  • The client approves a staging site before you switch the domain.
  • What you monitor after launch, for how long, and what happens if clicks fall.
  • How long the old site stays available as a fallback, and who pays for it.
  • No guarantee of rankings or traffic in the contract.

Have a lawyer review your wording. This is information, not legal advice.

Where Ploy fits, and where it does not

Ploy is one option. Its Starter plan is $50 a month ($480 a year) with 4,000 AI credits a month, and Pro is $300 a month ($2,880 a year) with 24,000, as of November 2026. Credits do not roll over, and Ploy publishes no price per action, so test one real page set before you quote a client. Its docs also say a repo-based migration done with your own coding agent uses no Ploy credits.

  • It fits when the client wants a modern marketing site, can accept a rebuild on a new design system, and the old site is mostly pages and posts.
  • Another route is better when the site has a lot of custom plugins, membership features or ecommerce, when the client needs a white-label portal (its public pages describe none), or when you need a published uptime promise. A WordPress to WordPress move on a new host is often cheaper and safer.

Whatever you use, a person must review every page. AI-written or AI-rebuilt pages can contain mistakes, and Google judges pages on quality and value, not on the tool used. See how Ploy site migration works and whether Google penalizes AI-written pages.

How I'd approach this

I would sell it as a paid audit first. The audit result (page count, redirect map size, forms, what cannot be moved) tells you the price, and the client sees you doing the careful part before any rebuild. Then I would offer the Light or Standard fixed scope, with monitoring included. If you want the repeatable parts, such as intake forms, status updates to the client and a post-launch check list, to run on their own, Blur Studio builds the custom version, including AI agents that use your business knowledge, CRM and calendar connections, and ongoing care.

First-week plan. Day 1: write a one-page offer with the four steps and the three scope levels. Day 2: build a reusable audit sheet and redirect-map template. Day 3: pick one real or friendly site and run the audit, including a crawl and a Search Console export. Day 4: test your rebuild route on a small page set, including a Ploy workspace if you want a comparison, and note credits used and pages you had to fix by hand. Day 5: send three offers to clients or prospects with a clear problem. Decision rule: take on a migration only if the client will give you domain and Search Console access before you start.

I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.

Questions people ask

What is website migration as a service?

It is a fixed-scope project where you move a client's site to a new platform and protect their search traffic while doing it. The steps are an audit, a redirect map, the move and post-launch checks.

How much should I charge to migrate a client website?

It depends on pages, forms, ecommerce and content work. Sellers publish ranges from about $1,500 to $35,000 and Goodspeed says its migrations start from $10,000, so price by scope, and charge for a paid audit first. See how much a website migration costs.

Will moving a client's site hurt their rankings?

It can. Google says permanent redirects do not cause a loss in PageRank, but results can take a few weeks or more to settle, and studies of domain moves show long recovery for many sites. Never promise a result. See the SEO migration checklist.

Can I export a Wix or Framer site to another host?

Wix's help center says the site must run on Wix's servers, and Framer says it offers no HTML export for self-hosting. In both cases the move is a rebuild. Check each vendor's current help page before you quote.

Can an AI tool do the whole migration?

It can speed up the rebuild, but not remove the checking. Ploy's docs describe its migration as a rebuild, not an identical copy, and say forms, plugins, custom code and private pages may need separate work. A person must review every page. See how Ploy site migration works for its limits.

How long should I keep monitoring after launch?

Six to eight weeks is a sensible minimum for a standard site. Google says it can take a few weeks or more for medium-sized sites to move in results. If you changed domains, Google advises keeping redirects at least 180 days.

Who should own the domain during a migration?

The client. Get registrar, hosting, analytics and Search Console access in their name before you start, and keep the old domain registered for at least a year after any domain change, per Google's guidance. See who owns your website code.

Should I use Ploy for every migration?

No. It fits simple marketing sites you are happy to rebuild on its design system. Sites with heavy plugins, ecommerce or membership features, or clients who need a branded portal, are often better on another platform. Check Ploy's current pricing and test one site first.

More in this topic: Websites: AI, client sites and agency delivery (7 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…