A website move and a mailbox move are different tasks. Start by identifying what should move and what should stay with its current provider, so the website plan accounts for your email and other domain services.
1. Explain what you have now
- Give Trilogy your website address and the names of your hosting, domain, DNS and email providers.
- Say what the website runs on, if known, and identify important forms, shops, booking tools or other integrations.
- Explain whether email should stay where it is or whether you want mailbox migration assessed separately.
- Mention any known website faults, access restrictions or changes already planned.
Do not include account passwords or recovery codes in the initial enquiry. Trilogy can review what information and access are needed before work is agreed.
2. Agree the move before changing anything
Trilogy reviews the website, hosting, DNS, email and technical dependencies. The required changes are agreed with you before Trilogy handles those agreed DNS changes. Keep existing services in place while the move and its checks are being planned.
3. Prepare and test the website
The published Trilogy move approach is to create a source backup, prepare the destination without changing the live website, then check key pages, forms, SSL and WordPress access where applicable before cutover. Tell Trilogy which customer journeys are most important to check.
4. Switch and check the result
Only the required website records are changed, with a practical rollback path retained. Relevant email DNS records are preserved wherever practical. This is not a promise of zero downtime or a fixed DNS propagation time.
After the agreed switch, check the website and any important forms. If email remains with its existing provider, also check sending and receiving. Report unexpected behaviour to Trilogy; do not cancel the old service until the remaining dependencies and next steps have been agreed.
