Included in a typical proposal
- Inventory and copy to the named destination.
- DNS change labour you authorise.
- Validation of named journeys.
WEB DESIGN & DEVELOPMENT
Website migration
in Dubai & the UAE.
Move your website with a clear plan for files, databases, domains and important integrations. Prepare the destination and validation steps before changing live traffic.
WHAT THIS SERVICE IS
A plain explanation of the work.
Website migration is moving a working site to a new host, a new account, or sometimes a new domain, without losing mail, certificates or the URLs you need. It is a planned change with an inventory, a copy, a switch, and a check. It is not “FTP the files on Friday and see”.
The difficult parts are usually DNS, email on the same domain, cron jobs, and environment-specific configuration. A WordPress site that hard-coded the old domain in the database needs a careful search-replace. A static site is simpler but still needs HTTPS and redirects.
Downtime can be near zero with hosts that allow overlap, or it can be a short window if the old server must be switched off. We will state which case you are in rather than advertise a number we cannot see yet.
A CLEAR PICTURE
A labelled diagram, not a decoration.
- Domain & DNS What still points where, including mail.
- Files & database The site copy on the new host.
- Certificates & HTTPS Names that must match after the switch.
- Checks & overlap Journeys proven before the old host is cancelled.
WHO IT IS FOR
The situations this page is written for.
Businesses leaving a slow or closing host, teams taking a site back from a developer’s shared account, and organisations consolidating several small sites. Also anyone whose mail and website currently share a fragile cPanel they are afraid to touch.
- WordPress sites on outdated PHP at the current host.
- Companies that must keep mailboxes live during a website move.
- Teams changing domain after a rebrand, with a redirect plan.
- Owners who finally have registrar access they used to lack.
TYPICAL SCOPE
What a proposal usually names.
01
Migration inventory
Files, databases, cron, SSL, DNS, email, CDNs, and third-party callbacks that still point at the old IP. Staging copies and licences tied to a domain are listed.
02
Destination preparation
Build the new environment, matching PHP or runtime needs, and copy the site. Hosting accounts are in your name. We do not migrate you into a personal account of ours as the only copy.
03
Change planning
TTL, the switch moment, and a rollback if the old host can still serve. Email MX records are treated as sacred unless the brief includes moving mail too.
04
Post-move validation
Pages, forms, admin login, certificates, and a sample of old URLs. Search Console and analytics need the new property ownership confirmed as yours.
HOW THE WORK RUNS
The sequence we follow once the brief is clear.
-
Inventory including mail
A website-only move that breaks mail is a failed move.
-
Copy and compare
On the destination, with a hosts-file or staging test.
-
Switch DNS with a watch
Someone available who can reverse the record.
-
Retire the old account on a date
Not the same hour, if you can still pay a week of overlap.
INCLUDED AND QUOTED SEPARATELY
Labour versus things that sit on their own line.
Quoted separately
- The new hosting contract.
- A redesign “while we move”.
- Moving email if not in the proposal.
- Application refactors required by a newer PHP that break plugins.
AFTER HANDOVER
What you should hold when the work is done.
Old host access can be closed after the agreed overlap. Billing for two hosts during overlap is expected and should be in your head before we start.
Callback URLs at payment providers and webhooks must be updated; we will list the ones we know. Ones hiding in a plugin setting sometimes appear a week later — tell us if a feature suddenly “goes to the old site”.
PRACTICAL NOTES
Details that usually affect the proposal.
Licences tied to a domain or IP — some page builders, some CDNs, some payment webhooks — break until they are told the new home. The inventory should catch the ones we know. The ones hiding in a forgotten plugin setting appear when a feature is used. Budget a short watch window, not a same-hour cancellation of the old host.
Staff bookmarks, QR codes on vans, and email signatures still pointing at an IP or an old preview URL are operational leftovers. We can include a short list if you supply the materials. We cannot visit every vehicle. Tell sales the cutover morning so they are not sending the dying address.
PLANNING THE WORK
Questions worth asking.
Will email go down?
Not if MX stays put and we only move the website. If mail is on the same server we are emptying, the plan must include it. Say which you need.
Can we change domain at the same time?
Yes, with redirects from the old domain. That is more DNS and more testing. It is still one project if you want it combined.
Do you need our registrar password?
We need enough access to change the records in the proposal. A temporary invite is better than emailing a password.
CONNECTED SERVICES
Explore the next piece.
LET’S BUILD WHAT’S NEXT
Your next step starts
with a conversation.
Tell us what you want to improve, build or simplify. We’ll help you define a practical way forward.
Discuss your project