Moving a website or business system to a new server or cloud provider looks simple until something breaks. A forgotten scheduled task stops sending invoices, email stops arriving because a DNS record (the setting that points your domain to the right server) was missed, or the copied database turns out older than expected and recent orders are lost. Such failures come from dependencies nobody listed and from having no plan for going back.
Kemlat reviews the current environment and everything it depends on, then writes a migration plan that includes a rollback step. We build and test the new environment before users see any change, rehearse the move, and switch over at an agreed quiet time. Afterwards we check the system, the data and the email, and keep the old environment available until you confirm that everything works.
How we work
- 01
List dependencies and assess
We record everything the system relies on: software versions, databases, files, scheduled tasks, connections to other systems, DNS records, email and the SSL certificates that secure connections to your site. We check what the target environment supports and note the risks.
- 02
Plan the move and rollback
The plan sets the order of steps, the switch-over time, who does what, how data stays consistent, and the exact conditions for returning to the old environment. You approve it before work starts.
- 03
Build and test the new environment
We set up the target environment and load a recent copy of the data. Your team tests the main functions there while the old system keeps running.
- 04
Rehearse and switch over
We rehearse the steps first. Well before the switch we shorten the time other servers keep your old DNS settings in memory, so the change reaches users quickly. At the agreed time we pause changes on the old system so nothing entered during the copy is lost, make the final data copy and point the domain to the new environment.
- 05
Verify after the move
We check the application, record counts, scheduled tasks, email delivery and certificates, and watch the logs closely. The old environment is kept until you confirm, then closed and its data deleted or archived as agreed.
What you receive
Assessment, migration and rollback plan
A documented list of dependencies and a step-by-step plan with clear conditions for rollback.
Tested new environment
The target environment built, loaded with data and tested by your team before the switch-over.
Managed switch-over
The final data copy and DNS change carried out at the agreed time, with your team kept informed at each step.
Post-migration verification report
A record of the checks made after the move, the issues found and how each was resolved.
What changes for you
- Your system runs in the new environment with its data, email and connections working.
- Users experience a planned, announced switch-over rather than an unexpected outage.
- A planned route back to the old environment stays available until you confirm the move.
- You have an accurate record of the new environment and everything it depends on.
Where this service sits in the KEMLAT Method
Scope: Hosting, cloud and licence fees for the new environment are paid separately. Upgrading or rewriting the application itself is not part of a migration unless agreed, but we will tell you if the new environment requires it.
Questions clients ask
Will our site or system be offline during the move?
Most moves need a short pause while the final data is copied, scheduled at a quiet time and announced in advance. Some systems can move with almost no pause, and the assessment tells you which case applies.
What if something goes wrong after the switch?
The plan sets clear conditions for rolling back, and the old environment stays available until you confirm. If a serious problem appears, we return to the old environment, carry back any data entered since the switch, fix the cause and repeat the move.
Do you also move email?
Yes, if it is in scope. Email needs its own plan for mailboxes, DNS records and the SPF, DKIM and DMARC records that help receiving servers confirm your email is genuine, so we plan it together with the website or system.
What do you need from us?
Access to the current and new environments, contact with any developer or provider who built the system, and a person who can test the main functions and approve the switch-over.
Related services
All servicesStart with a conversation
Tell us where you are today. We will suggest the right first step, with no obligation.