How to Migrate a Website After Buying It: The Complete Technical Transfer Checklist

Deal Alert AI is reader-supported. We earn commissions from affiliate links at no cost to you.

This post is based on a video from our Deal Alert AI YouTube channel. Watch the original or read the full breakdown below.

The purchase agreement gets signed. The funds release from escrow. Everyone shakes hands over Zoom. And then you're sitting alone with a spreadsheet of logins, a WordPress admin panel you've never seen before, and the sudden realization that you are now personally responsible for keeping a revenue-producing asset online.

Migration is where deals quietly go wrong. I've watched buyers negotiate hard for eight weeks, shave $40,000 off an asking price, and then lose more than that in the first ninety days because they moved the site to a cheap host, changed the theme, and forgot to update affiliate tracking links. The deal math was perfect. The execution was not.

This guide is the migration playbook I use and recommend. It's organized into four phases, it assumes you're not a full-time developer, and it's built around one principle: the goal of migration is that nothing changes except who gets paid.

Why Migration Deserves as Much Attention as Due Diligence

Buyers obsess over the P&L. They'll spend three weeks reconciling Stripe payouts against a seller's Google Sheet and forty minutes thinking about how the site will physically move from one server to another. That ratio is backwards, because the P&L describes a past you can't change and migration determines a future you can.

Think about the asymmetry. If you find a $2,000/month discrepancy in the financials during due diligence, you renegotiate or walk. Annoying, but recoverable. If you break a site during migration and drop from position 3 to position 11 for your money keyword, you may spend six months and $15,000 in content and links climbing back — and some sites never fully recover. The downside is bigger and it's entirely self-inflicted.

The other reason migration matters more than people think: it's the only part of the acquisition where the seller's cooperation is both essential and expiring. Once the transaction period closes, that person's incentive to answer your Slack messages drops to roughly zero. Every credential you didn't collect, every undocumented cron job, every "oh, that plugin is licensed under my personal Gmail" becomes your problem. Marketplaces like Empire Flippers build a structured migration period into their process with a dedicated migration team, which is a genuine part of the value they provide. On Flippa, where more deals are peer-to-peer, you need to write that support window into the purchase agreement yourself.

Phase One: Build a Complete Asset Inventory Before You Close

Migration planning starts during due diligence, not after closing. Before you sign anything, you should have a written inventory of every single asset that makes this business work. Not "the website." Every account, every subscription, every API key, every login.

Here's what surprises first-time buyers: a $180,000 content site can easily depend on fifteen to twenty separate third-party accounts. The domain registrar. The host. Cloudflare. The email service provider. Three or four premium plugin licenses with annual renewals. A stock photo subscription. A rank tracker. A link-building retainer. Two affiliate network accounts. A Google Analytics property, a Search Console property, a Google Ads account with a remarketing audience in it. A Pinterest account with 40,000 monthly viewers driving 8% of traffic. Miss any one of these and you've bought an incomplete business.

The inventory should list, for each asset: what it is, who currently owns it, what it costs per month or year, whether it transfers or needs to be recreated, and who's responsible for moving it. Some things transfer cleanly (domains, hosting accounts). Some things can't legally transfer and must be recreated (certain plugin licenses, some SaaS accounts). Some things transfer but need a billing update. Knowing the category for each item before closing is what separates a two-day migration from a two-week fire drill.

This is exactly the kind of pre-work that should inform your offer. When we surface listings at Deal Alert AI, part of what we're looking at is the technical stack behind the business — the platform, the hosting profile, the visible third-party dependencies — because a WordPress affiliate site on standard shared hosting is a two-hour migration and a custom Node application with a Postgres database, three microservices, and a Redis cache is a project that needs a developer and a budget.

The Complete Pre-Migration Checklist

Work through this list during due diligence, not after. Every item should be confirmed in writing with the seller before funds release from escrow. If the seller resists on more than one or two items, that's information about how the rest of your relationship will go.

1. Full domain inventory. Not just the primary domain — every parked domain, every misspelling variant, every country TLD the seller registered. Get the registrar, the account email, and the expiration date for each one.
2. Hosting environment details. Provider, plan level, monthly cost, server specs, PHP version, and whether the site uses any server-level configuration (custom nginx rules, cron jobs, cached object storage) that won't survive a naive file copy.
3. Complete backup of files and database. Taken by you, or verified by you, before anything is touched. Store it somewhere the seller cannot access. This is your undo button.
4. Email service provider access and list export. Confirm the list size, the actual engaged-subscriber count, and whether the list can transfer or must be re-imported. A re-imported list often needs a warm-up sequence to avoid deliverability damage.
5. Every software subscription and license. Premium plugins, themes, SaaS tools, CDN, security services. Note renewal dates and whether the license is transferable or must be repurchased under your account.
6. All API keys and integrations. Payment processors, analytics, affiliate networks, third-party data feeds, Zapier or Make automations. Document what each key does before you rotate it.
7. Analytics and Search Console property access. You want to be added as an owner on the existing properties, not handed a new blank property. Historical data is part of what you're buying.
8. Affiliate and monetization accounts. Amazon Associates, network accounts, direct advertiser relationships, ad network accounts (Mediavine, Raptive, AdThrive). Understand which links need to be swapped to your IDs and how many there are.
9. Social media accounts and any owned communities. Facebook groups, Pinterest, Instagram, YouTube, Discord. Platform transfer rules differ wildly — some require the original owner to transfer ownership through a specific flow.
10. Content and asset repositories. Code repos, design files, original images, standard operating procedures, freelancer contact lists, content briefs, keyword research spreadsheets.
11. Documented operational routines. What does the seller actually do every week? Publishing schedule, backup routine, plugin update cadence, anything that keeps the machine running.
12. A written migration timeline with dates, owners, and a rollback plan for each phase, agreed to by both parties before closing.

Phase Two: Domain and DNS — The Highest-Risk, Lowest-Effort Step

Your domain is the single point of failure for the entire business. Email, website, everything routes through it. Which is why the standard advice — "transfer the domain to your registrar immediately" — is often wrong for high-traffic sites.

A registrar-to-registrar transfer takes 5 to 7 days and involves unlocking the domain, generating an auth code, initiating the transfer at the receiving registrar, and waiting for approval. It usually goes fine. But during that window you have reduced control, and if the seller's registrar account has any complication — an expired verification email, a recent contact change that triggers a 60-day ICANN transfer lock, two-factor tied to a phone number the seller no longer uses — you're stuck in a support queue with a live business hanging on it.

The safer sequence for anything doing meaningful traffic: leave the domain where it is, take control of the registrar account itself (change the email and password to yours), and simply update the DNS records to point at your new hosting. That's a five-minute change with instant rollback. Once the site is stable on your infrastructure and you've watched it for two or three weeks, then start the formal registrar transfer. You've decoupled two risks that most buyers stack on top of each other.

Phase Three: Moving the Site Without Breaking It

The actual site move is more mechanical than most buyers fear, provided you follow the right order. The order is: back up, build the new environment, deploy, test on a temporary URL, then switch DNS. Never switch DNS first and fix problems live.

For WordPress — which is the majority of content and affiliate deals — the practical tools are All-in-One WP Migration for smaller sites, or a host-provided migration service. Most quality managed hosts (Kinsta, WP Engine, Cloudways, Rocket.net) will perform the migration for you at no charge as part of onboarding. Use that. Their teams do dozens per week and they'll catch things you won't. For sites with large databases, the plugin route can hit upload limits and you'll need to move files via SFTP and import the database directly through phpMyAdmin or WP-CLI.

For custom-coded applications, you need the full repository, the deployment process documented, environment variables listed, and ideally a staging deploy completed while the seller is still available to answer questions. If the business runs on a stack you don't understand, hire a developer for the migration. A $600 developer day is cheap next to a week of downtime on a business generating $9,000 a month — that's $2,100 in lost revenue plus whatever rankings damage follows.

Testing on a temporary URL before the DNS switch is non-negotiable. Check: does the homepage load, do internal links resolve, do images render, do forms submit, does checkout complete a real test transaction, do affiliate links redirect properly, does the search function work, do scheduled posts still publish, do the caching and CDN layers behave. Crawl the staging site with Screaming Frog and compare the URL list against a crawl of the live site. Any URL that exists on live and not on staging is a page you're about to lose.

Phase Four: Email, Subscriptions, and the Money Plumbing

Once the site is stable, you move the accounts. This phase is less technically risky but it's where revenue quietly leaks if you're sloppy.

Start with monetization, because that's where money is actively flowing to the wrong person. Every affiliate link on the site pointing at the seller's tracking ID is a commission you earned and they collected. On a 400-page Amazon affiliate site, that could be 3,000+ individual links. Use a search-and-replace tool on the database (with a backup taken first) or a link management plugin to swap IDs in bulk. Then spot-check twenty links manually. For display ad networks, understand that Mediavine and Raptive require a new application under your entity — the account does not transfer — and there's typically a payment gap of 30 to 60 days during the switchover. Budget for it.

Then the email list. If the ESP account transfers directly (Klaviyo, ConvertKit, and Mailchimp all allow ownership changes), that's the clean path — your automations, tags, and sending reputation move intact. If you have to export and re-import into your own ESP, your sending domain changes and your deliverability reputation resets to zero. Warm it up: start by mailing your most engaged 500 subscribers, then expand over two weeks. Blasting a cold 40,000-person import on day one is how you land in spam folders permanently.

Finally, the subscription cleanup. Move every recurring service to your own payment method and your own email address. Then audit it. In almost every acquisition I've seen, there's $50 to $300 a month of subscriptions the seller was paying for that the business doesn't actually need — an abandoned SEO tool, a duplicate backup service, a Canva Pro seat nobody uses. That's found money. On a 3.5x multiple, cutting $150/month in dead subscriptions adds about $6,300 in enterprise value for an hour of work.

The Mistakes That Actually Cost Buyers Money

Four failure modes account for the overwhelming majority of post-acquisition traffic losses, and all four are avoidable.

Redesigning too fast. New owner takes over, hates the 2019 theme, installs something modern in week two. The site's HTML structure changes, internal linking changes, page speed changes, Core Web Vitals change. Google re-crawls and re-evaluates. Sometimes it's fine. Sometimes rankings slide for eight weeks and you have no idea whether it was the theme, the migration, or an algorithm update, because you changed everything at once. Do one thing at a time, and wait.

Missing 301 redirects. If any URL changes during migration — trailing slashes, HTTP to HTTPS, www to non-www, a different permalink structure — you need a 301 redirect from old to new. Missing redirects mean 404s, and 404s on pages that hold backlinks mean you've thrown away link equity you paid for. Crawl before, crawl after, diff the lists.

Database corruption and serialized data. WordPress stores serialized arrays in the database. A naive find-and-replace on the domain name breaks the serialization and produces silent failures — widgets vanish, theme options reset, page builder content turns into raw shortcodes. Use WP-CLI's search-replace command or a tool like Better Search Replace that handles serialization correctly. And back up first.

DNS propagation impatience. Changes take 24 to 72 hours to propagate globally. During that window, some visitors hit the old server and some hit the new one. If both servers are live and the site takes orders, you can end up with transactions split across two databases. Keep the old server running and read-only if possible, lower your TTL to 300 seconds a full 48 hours before the switch so propagation happens faster, and schedule the cutover for your lowest-traffic window — for most US-focused sites that's Saturday or Sunday around 3 AM Eastern.

Plan the Migration Before You Make the Offer

The best migrations are boring, and they're boring because the buyer knew exactly what they were buying at a technical level before they made an offer. That's a diligence question, not a post-closing scramble.

When you're evaluating a listing, the technical stack should shape both your price and your timeline. A standard WordPress affiliate site on shared hosting with a handful of plugins is a weekend project. An ecommerce store on Shopify is mostly an account transfer and barely a migration at all. A membership site with recurring subscriptions, a custom payment integration, and a member database is a serious undertaking where a failed migration means angry paying customers, chargebacks, and churn. A SaaS product with real infrastructure needs a developer involved from the LOI stage.

That's why we built the technical profile into the listing intelligence at Deal Alert AI. When a deal surfaces, you can see the platform, the hosting signals, the visible integrations, and the general complexity class before you've spent an hour on it. It lets you filter for the kind of migration you're actually capable of executing, and it lets you price complexity into your offer rather than discovering it after the wire clears.

Whether you're browsing curated inventory on Empire Flippers, sorting through the wider market on Flippa, or tracking listings across every marketplace through Deal Alert AI, treat the migration plan as part of the deal, not an afterthought. Write the asset inventory during diligence. Get the support window in the contract. Back up everything twice. Move one variable at a time. Then leave it alone for thirty days and let the asset you paid for do what it was already doing.

By Sophal Lanh, Founder of Deal Alert AI