Migration safety
A migration normally copies data rather than changing the source service. Keep an independent backup and leave the source online until the new website, databases and email have been tested.
Source remains intactCopying should not replace the original.
Keep your own backupRetain a recovery copy outside either server.
Share access securelyUse temporary credentials and remove them afterwards.
Safety model
UKC prepares a separate destination copy where the source platform permits. Files, databases and mail are checked before DNS is changed. Dynamic content may need a final synchronisation during a short maintenance window.
Your safeguards
Scope
External email, DNS, licence keys, payment callbacks, cron jobs and remote storage may not be included in a website copy. List them in the migration request.
Article feedback
