1. Enable migration requests only for products where your team intends to provide the service.
2. Review the request form and explain what source access is needed for the migration types you support.
3. Submit a controlled test request and verify that staff can find the service, domain and supplied details.
4. Check the Migration Update email and the customer's view of status and replies.
5. Define who accepts requests, performs the move and approves the final result.

Review the submitted scope before accessing the source. Establish whether files, databases, email, DNS or application-specific data are included, and agree on the destination and cutover approach. The module limits active requests per service, so update the existing request instead of asking the customer to create several for the same work.

Use the supplied status workflow, including Submitted, In progress, Waiting, Completed, Declined or Cancelled as appropriate. When waiting for the customer, ask a precise question and explain what remains blocked.

Use the protected credential fields rather than asking the customer to paste passwords into a normal message. Stored source credentials are encrypted, and an administrator's reveal action is explicit and audited. Restrict access to staff performing the migration.

After the work closes, follow the workflow that removes retained source credentials and ask the customer to revoke temporary access where appropriate. Do not keep a private copy in an unrelated note or spreadsheet.

Test the destination website before changing live DNS. Check files, database content, logins, forms and other business functions included in the agreed scope. For email migrations, verify mailbox content and delivery separately.

Plan the final data sync for sites receiving orders or user changes. A copy made earlier may not contain the latest live data. Confirm the DNS and certificate arrangement and retain a recovery route during the cutover.

Tell the customer what was moved, what was tested and any remaining action they must take, such as changing external nameservers. Mark Completed only after the agreed acceptance checks pass. Keep safe timestamps and scope notes for later support, while removing credentials that are no longer required.

• Configure and interpret Hosting Suite site-health monitoring
• Set a WordPress update policy and validate changes in staging
• Configure Hosting Suite access rules and verify effective permissions
• Customize Hosting Suite emails and control automatic template updates