We’ve moved sites off shared hosting, off a former developer’s personal account, and off platforms nobody has the login for any more. The first step is always the same: find out what actually exists.
We find every moving part: domain and registrar, DNS, mail, the app itself, its data, certificates, cron jobs, and whatever undocumented thing is quietly load-bearing.
Output
A written inventory of what exists and who
currently controls it, often the first time anyone has had that list.
We stand the environment up fresh and documented rather than copying a mystery configuration forward. Old problems don’t get imported.
Output
A named environment running your site in
parallel, on a URL you can click, before anything changes publicly.
You review the parallel copy. We lower DNS TTLs ahead of time, cut over, and watch it. The old environment stays reachable until you’re confident.
Output
A cutover with a rollback path, not a leap.
From here the same team that runs the server is the team that changes the site. There is no ticket to open with a second company.
Output
One relationship instead of two, and
documentation you could hand to somebody else if you ever wanted to.
The site works, nobody has the credentials, and everyone is afraid to touch it. We start by recovering control of the domain, then work inward.
The classic split. The host says it’s the code, the agency says it’s the server. Consolidating removes the argument entirely.
It was fine at launch and it isn’t now. We size the environment to what the traffic actually looks like, then bill on the average.
Migration is scoped from the inventory, so we can tell you the number before anything changes. If the inventory reveals it’s more tangled than either of us expected, you hear that before you commit, not after.
And if you ever want to leave us, you own your domain, your code and your content. We’ll help you hand it over.
No more “that’s the other vendor’s problem.”