A PLAIN GUIDE
A planned move
Moving off an old website platform
A move off an old site starts with a written plan.
The first job is a list of the pages, a map of the addresses, the access the move needs, and a checklist for launch day.
Set the inventory earlier
Here’s the deal. Mark wants the page list, the address map, the access the project needs, and the launch checklist settled before the build is far along.
He has no written account of a last move that went wrong. The earlier start is how he wants the work arranged.
Rebuild on the platform he supports
When the project fits, the new site is built on the platform Mark builds and supports. Client sites are not left on Wix, Squarespace, or WordPress for him to maintain.
Why ongoing work stays on that platform is in why one website platform.
Keep the pages that still help
Useful pages should come along. He reviews the current addresses and how they perform, keeps the addresses that still belong, and writes down where each necessary change should land.
The same checks run before the site goes public and again after launch. He looks at where old addresses send people, whether the copy is complete, whether links inside the site still work, whether search engines are allowed to index the pages, and whether the inquiry forms deliver.
How a mountain website is scoped is on web development.
Risks to test
No finished migration example is on file, and none includes a measured result. No particular failed move is documented either.
The launch review looks for missing pages, links that fail, addresses that point to the wrong place, a block that keeps search engines out, and forms that do not send the inquiry.
What the customer should know
What’s the bottom line. Three facts should be settled with you first: the parts of the site that will change, who owns each account, and the work this move covers.
No one should promise that rankings will sit still. The plan should cut down the problems that can be avoided and leave a way to recover if something fails.
Ownership on a new website is in what to expect with a new website.
Backups, a baseline, and a dated launch log
Real quick. Hold on to backups, a baseline report from before launch, and a launch log with the date on it.
How many days it takes is its own question. It follows how large the job is, which other tools have to connect, and whether the content is ready. The ordinary timing quoted for a fresh website build stays on the expectations page. It does not carry over as a deadline for every move.
Monthly plans are on pricing.
Questions can go through contact.
In Mark's words
Mark Kendrick, Kendrick Mountain Consulting, answering in his own words.
What I would change
I would establish the content inventory, URL map, access requirements, and launch checklist earlier in the process. I do not have a documented last-migration incident to describe as the reason for that improvement.
A real example
My stated approach is to rebuild on the platform I support when that fits the project, rather than maintain Wix, Squarespace, or WordPress.
How I handle it
To preserve useful pages, I would inventory existing URLs and performance, retain appropriate addresses, and map necessary changes to relevant replacements. Redirects, content, internal links, indexing settings, and forms need testing before and after launch.
What I learned
The problems I would specifically check for include lost content, broken links, incorrect redirects, blocked indexing, and failed inquiry forms.
What you should know
Before you move your site, know what is changing, who owns the accounts, and what the migration includes. No one should guarantee zero ranking movement. The plan should reduce avoidable problems and make recovery possible if something fails.
What else helps
It would also help to retain backups, baseline reports, and a dated launch log. The schedule depends on scope, integrations, and content readiness; a general website-build estimate should not automatically become a promise for every migration.
Related
- Why one website platform for ongoing mountain marketing
- Web development
- What to expect with a new website
- Monthly plans
- Contact Mark Kendrick
- Redesigning a website without losing Google rankings
Questions
Does Mark maintain Wix, Squarespace, or WordPress?
No. When a move fits, he rebuilds on the platform he supports.
Will rankings stay the same after the move?
No one should guarantee that. The plan leaves room to recover.
How long does a migration take?
It depends on scope, integrations, and content readiness.
Is there a migration case study?
No completed example with a measured outcome is on file.
Ready to plan the move?
Tell Mark which pages should survive the move. Call (909) 443-2260.