For a small business site, plan two to six weeks for a CMS migration from setup through post-launch fixes. A CMS is the software you use to create, edit, and publish website pages, such as WordPress or Drupal.
That range covers content transfer, design setup, redirects, testing, and launch. A very simple brochure site can finish near the short end. Custom layouts, online ordering, membership areas, or messy old content push the work toward the long end.
Official resources:
- Follow Google's site-move checklist for URL changes — Verify expected recrawl timing, redirect mapping, and monitoring steps before setting a migration schedule.
- Use Google's hosting-move guide when URLs stay the same — Check preparation, DNS, and traffic-monitoring steps for CMS or hosting moves without URL changes.
Table of Contents
- What does the timeline include?
- Why do small sites still take weeks?
- How do you protect traffic and leads?
- How should you sequence the work?
- Frequently Asked Questions
What does the timeline include?
A migration is more than copying text from one place to another. It includes inventory, content export and cleanup, design rebuilding, settings and user accounts, URL mapping, testing, launch, and fixes after launch.
Post-launch work matters because small problems often appear only on the live site. Plan time for broken links, missing images, form failures, and display issues on phones. A launch without a fix-up window is unfinished.
Why do small sites still take weeks?
Small page counts can hide real work. Old pages often need rewriting, new image sizes, better headings, and clearer calls to action. Menus, sidebars, footers, and contact details also need rebuilding in the new system.
Features add time even when pages are few. Contact forms, maps, newsletters, booking tools, shops, donations, and member logins each need setup and testing. Replacing one add-on with a different one takes longer than keeping the same function.
How do you protect traffic and leads?
Keep a list of every old address and decide where each one should point in the new site. Set up permanent redirects before launch so visitors, bookmarks, and search listings reach the right pages. Test the most visited pages, service pages, and contact page first.
Check everything that turns a visit into an inquiry. Submit each form yourself, confirm confirmation messages and email alerts, and check phone numbers, hours, directions, and tracking codes for paid campaigns. Fix front-end details too, including mobile menus, buttons, fonts, and page speed.
How should you sequence the work?
A clear order prevents rework and missed pages. Keep content frozen or tracked once export begins.
Assign one person to approve content and one person to approve the design. Shared approval keeps decisions fast and prevents last-day rewrites.
- Inventory pages, files, forms, users, and connected tools.
- Clean and finalize content before moving it into the new design.
- Build pages, menus, redirects, forms, and tracking in a private test site.
- Test on phones and computers, fix issues, then launch and monitor closely.
Frequently Asked Questions
Should publishing pause during migration?
Avoid major edits after content export begins. Record small needed changes in one list and apply them once, after testing.
Can you keep the same design?
You can match the look closely, but most systems need new templates, menus, and styling. Treat it as a rebuild with a familiar design, not an exact copy.
When should you delay launch?
Delay when forms fail, redirects are missing, key pages display poorly on phones, or tracking for inquiries is unconfirmed. Fix those before going live.
