Plan a Website Platform Migration Before Touching the Live Site in Baring

A platform migration should be planned before the live site becomes the workbench.

The old system is the source of current content, URLs, integrations, and business continuity. Preserve that state before changing it.

Inventory the existing system

Record:

• pages and posts;
• media;
• current URLs;
• forms;
• integrations;
• analytics;
• redirects;
• DNS;
• email dependencies;
• hosting;
• domain control;
• platform accounts;
• backups.

This inventory defines what the replacement must preserve or deliberately retire.

Define the destination structure

Decide how the new platform will represent existing content, structured data, navigation, forms, and other required features.

Do not begin migration by choosing a new theme and hoping the old content fits afterward.

Map URLs before implementation

Keep current URLs where the same content and intent remain.

Prepare explicit old-to-new mappings for genuine changes.

Google's current migration guidance recommends preparing the new site, testing it thoroughly, mapping old URLs to new destinations, and then implementing redirects for moved resources.

Establish staging and rollback

Build and test the replacement away from normal production traffic where practical.

Keep a current backup and document how to restore the old site or routing if the launch fails.

Define launch criteria

Before cutover, decide what must pass:

• key pages;
• redirects;
• forms;
• media;
• mobile layouts;
• analytics;
• HTTPS;
• DNS readiness;
• important integrations.

Also identify who has authority to make the final change.

For a related next step, see Export Business Website Content Before Leaving a Hosted Platform in Newark and Plan a Small-Business Website Before Choosing a Platform in Glenwood.

For authoritative guidance on this subject, see Google's guidance on site moves.

See Also

• Test a Replacement Website Before Switching the Domain in Edina

Switchboard can help Baring and Northeast Missouri businesses turn a platform migration into a controlled transition rather than a sequence of live-site experiments.