
Migration Website Checklist
A website migration moves far more than pages. This checklist covers the parts SEO checklists skip: content and files, forms and lead routing, integrations, analytics, user accounts, orders and legal pages, each with an owner and a test.
Sahar
Content Writer
This migration website checklist covers everything a website migration moves besides rankings. SEO checklists, rightly, focus on redirects and crawling. But a migration also moves your content and files, your forms and the emails they send, your integrations, your analytics and, on many sites, your users, orders and data. Those are the parts that break quietly: the redirects all work, rankings hold, and three weeks later someone notices that no quote requests have arrived since launch.
Need this done right?
Hoop builds the strategy, design and development behind sites like this one, talk to us about yours.
What This Migration Website Checklist Covers
This checklist covers six areas that every migration must move and test: content, forms, integrations, tracking, accounts and data, plus the legal and security basics. Work through it alongside the SEO side of the move, which our website migration checklist covers phase by phase.
| Area | What can break | Usual owner |
|---|---|---|
| Content and files | Missing pages, lost images and PDFs, broken formatting | Content lead |
| Forms and emails | Leads not delivered, autoresponders lost, spam floods | Marketing / sales |
| Integrations | CRM, chat, booking or payments disconnected | Developer |
| Analytics and tracking | Conversions missing or double-counted, pixels lost | Analytics / marketing |
| Users, orders and data | Accounts that cannot log in, history missing | Developer / operations |
| Legal, accessibility, security | Missing privacy pages, consent not recorded, exposed admin | Legal / developer |
Owners and a Website Migration Project Plan
Start with a website migration project plan that gives every area one owner. Ownership matters more than any tool: a website migration project usually involves a content team, developers, marketing, sales or customer service, and sometimes legal, and each assumes another team checked the thing that broke.
A practical plan has one row per area with four columns: the owner, the test they will run, the date it is due, and sign-off. Add a content freeze for the final days before launch, so the content you migrate is the content that exists on launch day. Agree how issues are reported and who can approve a delay if a test fails.
Content Inventory and Content Migration
Content migration is the largest part of most moves, and it starts with knowing exactly what you have.
Build the content inventory
A content inventory lists every page, post, file, image, video and download on the site, with its URL, owner, last update, traffic and links. Export what you can from the CMS, crawl the site to catch anything the CMS does not list, and include files that are linked from emails or documents but not from the site. PDFs are the classic casualty: they often carry backlinks and are forgotten in every website content migration.
Keep, merge, rewrite or retire
A migration is the best chance you will get to clean up. For each item decide:
- Keep: it performs and is accurate; move it as it is.
- Merge: several weak pages cover one topic; combine them into one stronger page.
- Rewrite: the topic matters but the page is out of date or thin.
- Retire: no traffic, no links, no purpose; remove it (and decide whether it needs a redirect).
The content migration plan
The content migration plan explains how each type of content moves to the new system. Map old fields to new ones (title, body, excerpt, category, tags, author, publish date, featured image), decide how rich text, embeds and shortcodes will be converted, and keep authors and original dates where they matter. Carry over image alt text and captions; they are easy to lose in an export. Use this short content migration checklist for every content type:
- Field mapping written and agreed.
- A sample of each content type migrated and reviewed before the full run.
- Formatting, links, images and embeds checked on the new templates.
- Authors, dates, categories and tags preserved.
- Alt text and captions present.
- Totals match: the number of posts, pages and files before and after.
Forms, Lead Routing and Emails
Forms are where migrations most often cost real money, because a broken form does not look broken. For every form on the site, record where it sends, who receives it, what the autoresponder says, which fields map to your CRM and what spam protection it uses. Then, on the new site:
- Submit every form, on desktop and on a phone, and confirm the submission arrives where it should.
- Check that the autoresponder is sent and reads correctly.
- Confirm each field lands in the right CRM field, including hidden fields such as source and campaign.
- Make sure spam protection works without blocking real people.
- Check the thank-you page or message, and that conversion tracking fires on it.
- Test transactional emails such as order confirmations, password resets and booking reminders, and check the sending domain is authenticated so they do not land in spam.
Integrations and Third-Party Scripts
List every integration and script on the old site: CRM, live chat, booking tools, payment gateways, maps, review widgets, newsletter sign-ups, search, heatmaps and ad pixels. Some are added through the CMS, some through a tag manager, some hard-coded into templates. For each, decide whether it moves, is replaced or is dropped.
The details that get missed are credentials and callbacks: API keys tied to the old domain, webhooks pointing at old URLs, allowed-domain lists in third-party dashboards, and payment providers that need the new domain approved. Test each integration with a real transaction or record, not just a page load. If your new site is a rebuild rather than a theme change, our website development team plans integrations as part of the build.
Analytics and Tracking (Including a GA4 Migration)
If tracking breaks, you cannot tell whether the migration worked. Keep the same analytics property and the same conversion event names, so reports stay comparable. Install tags on every new template before launch, check your consent banner still controls which tags load, and confirm ad pixels and conversion tags fire on the new thank-you pages.
If you are also moving to Google Analytics 4 or rebuilding your GA4 setup, treat that GA4 migration as part of the project rather than an afterthought: map your old goals to GA4 events, recreate key reports, and run old and new tracking in parallel for a period where possible. Our Google Analytics 4 setup service covers this.
After launch, compare at least a week of data with the same period before. A drop in conversions with steady traffic almost always means tracking, not customers, has changed.
Users, Orders and Website Data Migration
Sites with accounts, orders, subscriptions or bookings need a website data migration plan of their own. Decide what moves (customer accounts, order history, subscriptions, saved addresses, loyalty points, reviews), how it is transformed into the new system's structure, and how you will check it.
- Passwords: decide whether accounts can keep their passwords or need a reset, and prepare the reset email before launch.
- Rehearsals: run the data migration on a copy first, then check record counts and a sample of real records by hand.
- Live changes: plan for orders and sign-ups that happen between the final export and launch.
- Payments and subscriptions: confirm recurring payments continue and are not charged twice.
When we rebuilt BeesApp, a retail-tech platform in Saudi Arabia, the data was migrated from a fragmented PHP, Django and Vue system into a new architecture with 120+ documented API endpoints, and the platform ran at 99.9% uptime after launch. The BeesApp case study explains the approach.
Before the final export, freeze changes to accounts and orders where you can, or plan a short delta migration that copies anything created in the last hours. Afterwards, ask a handful of real customers or staff to log in and check their own history; they will spot problems a test account cannot.
Plan customer communication for any change they will notice, such as new log-in steps or a new account area, so support is not surprised by the questions.
Legal, Accessibility and Security
- Legal pages: privacy policy, terms, cookie policy and any required notices are present and up to date.
- Consent: the cookie banner works and its choices are respected by every tag.
- Accessibility basics: headings, alt text, form labels, contrast and keyboard navigation on the new templates.
- Security: a valid SSL certificate, HTTPS everywhere, admin access limited to the people who need it, old staging and admin URLs closed, backups running.
Website Migration Testing Before Sign-Off
Website migration testing works best as a script: a written list of tests for each area, who runs them and what "pass" means. For example, "Contact form: submit on iPhone and Android; email arrives in the sales inbox within one minute; lead appears in the CRM with source set; thank-you page loads; conversion recorded." Vague tests such as "check forms work" get ticked without being done.
Run the script on staging, fix what fails, and run it again on the live site immediately after launch. Keep the results; they are useful evidence if something is questioned later.
A sample test script
| Area | Test | Pass means | Tester |
|---|---|---|---|
| Contact form | Submit on desktop and on a phone | Email arrives in the right inbox; lead appears in the CRM with its source; thank-you page loads; conversion recorded | Sales |
| Checkout | Place a test order with a discount code | Order, payment, confirmation email and stock update all correct | Operations |
| Accounts | Log in with a migrated account; reset a password | History visible; reset email arrives and works | Customer service |
| Content | Open ten migrated posts of each type | Images, links, embeds and formatting intact | Content lead |
| Tracking | Run each conversion once | Each recorded once in analytics and ad platforms | Analytics |
| Integrations | Trigger chat, booking and newsletter sign-up | Each reaches its connected system | Developer |
Website Migration Tools
A handful of website migration tools cover most of this checklist:
- Site crawlers to build the content inventory and check links and pages on the new site.
- CMS export and import tools to move content in bulk with field mapping.
- Tag checkers and browser developer tools to see which tags fire on each page.
- Form and email testing tools to confirm delivery and spam scores.
- Uptime and error monitors to alert you after launch.
- A shared spreadsheet or project board for the inventory, the plan and the test script.
Whatever tools you use, keep one shared record of the inventory, the decisions and the test results. When someone asks months later why a page was removed or where a form now sends, that record is the answer.
Then Run the SEO Checklist
With content, forms, integrations, tracking and data covered, run the SEO side of the move: the redirect map, staging crawl and monitoring in our website migration checklist, and the extra checks for your type of move in the site migration checklist. For launch day itself and rollback planning, use the launch-day checklist.
Moving your site? Get a free SEO audit before you migrate. Our SEO migration services cover the rankings side, and our developers can handle the content, integrations and data in the same project.
“Redirects protect your rankings. Testing protects your leads, orders and data.”
Key takeaways
- 01Build a content inventory of every page, file and image, and decide to keep, merge, rewrite or retire each one
- 02Test every form end to end, including where it sends, autoresponders and CRM fields
- 03Move integrations, API keys and tracking deliberately, and compare a week of analytics before and after
- 04Give every area one owner who signs it off after a written test, then run the SEO checklist
Written by
Sahar
Content Writer
Frequently Asked
Questions
Everything you need to know before booking a strategy call. Can't find your answer? Contact us directly.
Ask hoop
Usually replies in minutes
What is a content inventory?
A content inventory is a list of every page and asset on your website (pages, blog posts, PDFs, images, videos and downloads), with its URL, owner, performance and what will happen to it in the migration: keep, merge, rewrite or retire. It is the foundation of any content migration plan.
PEOPLE ALSO ASK
Swipe for 3 more questions →
Can't find your answer? Contact us directly.


