Moving a Website Without Customers Noticing
This month JAMARQ has been moving client websites from shared hosting to a newer platform. The standard for each move is simple to state and hard to meet: customers should not be able to tell anything happened.
September 18, 2026
Same answers, new home
A business website is a set of answers. Ask for the schedule, get the schedule. Send a reservation request, get a confirmation and a new entry in the admin. A successful move means the new site gives the same answers to the same questions.
Record the real questions
Instead of guessing which requests matter, record real ones. For a period before each move, requests to the old site are captured: page loads, form submissions, admin actions. That recording becomes the test suite, made of exactly what the site really does.
Replay and compare
The recorded requests are then replayed against the new version, and every response is compared with what the old site returned. Any difference is either a bug to fix or a deliberate change to confirm. Nothing switches over until the differences are understood.
Move the data carefully
The data moves separately and gets checked separately. Row counts should match, records should match, and the site should behave the same on top of them. On one site this month, thousands of rows moved in about an hour with zero differences in the checks afterward.
Switch over quietly
The actual switch happens late at night when traffic is lowest, with a way back ready if something goes wrong. When the testing has been done properly, the switch itself is short and uneventful.
Boring is the goal
A good migration produces no story for customers at all. The work is in making sure of that before anyone flips a switch.