The domain, customer and target server must match the supported ownership mapping. An alias or standalone DNS zone on your controlled backend is different from a live website owned by another account. This workflow is not a general migration tool for arbitrary hosting accounts.

1. Review the domain's current DNS zone, provider binding, cPanel alias or Plesk relationship and WHMCS customer.
2. Confirm that the new hosting service belongs to that customer and provisions on the expected mapped server.
3. Take a current DNS snapshot and identify records that must survive, especially external mail, verification and application records.
4. Enable and configure the supported hosting lifecycle integration before relying on it for customer orders.
5. Test the full transition with a controlled domain before applying it to production services.

The integration rechecks ownership and server details, preserves DNS, handles the verified DNS-only conflict around WHMCS provisioning and merges the approved records into the resulting arrangement. Open DNS Manager > Hosting transitions to inspect the plan and recorded outcome.

Do not manually delete the old alias while an automated transition is running. Doing so can remove the state the recovery plan expects. Read any failure before intervening.

Confirm the new account exists under the intended owner, the website document root is correct and certificates can be issued. Compare the final DNS with the preserved records. A successful account-creation callback does not prove that external email or every application subdomain survived as intended.

Check current public delegation as well. If DNS remains on another provider, local hosting-panel changes may not affect visitors until the authoritative records are updated.

The integration can restore the verified alias or standalone arrangement when supported recovery conditions hold. Review the exact recovery plan and current backend state first. A provider outage, ownership conflict or outside edit may require manual reconciliation.

Keep the domain's snapshot, transition reference and WHMCS provisioning error together. Resolve the underlying cause before retrying the same order. Creating another hosting account or changing the customer's owner to bypass a conflict can make the recovery more difficult.

Document whether termination should preserve DNS for another active service. Hosting cancellation and domain DNS retirement require separate policy decisions.

• Use a cPanel account username as the owner of parked DNS domains
• Use a Plesk subscription as the target for new DNS domain aliases
• Configure DNS backups and restore a reviewed record snapshot
• Configure DNS lifecycle cleanup with grace periods and protected zones