Move DirectAdmin hosting with ownership and scope intact.

Map users and reseller ownership first

Record which users belong to each reseller, the domains in each user account and the packages or custom limits that affect them. Decide the destination ownership before creating EzePanel accounts.

DirectAdmin backup levels and account archives describe source recovery. Review the data inside each export and rebuild the destination policy deliberately; copying a package label does not prove equivalent runtime limits.

Create the ownership structure before accounts

Decide which destination accounts belong to each reseller and which packages they may use. Confirm the effective account policy and required PHP runtime instead of assuming a copied package name reproduces the source limits.

The current product provides the destination hosting tools. A dedicated DirectAdmin archive importer or one-click account transfer is not currently provided; broader migration tooling is Planned.

Transfer one user’s recovery set at a time

Associate each source user’s website files and SQL exports with the correct EzePanel account. Create target databases and users within that ownership scope, import usable SQL and update the applications with their full destination credentials.

Preserve the source copy and inspect the import result. The EzePanel SQL import accepts .sql/.sql.gz within its upload limits; it is not a full control-panel archive importer or a guarantee of atomic rollback.

Verify the services belonging to each user

Reconcile every user’s domains, mailbox identities, DNS records, scheduled commands and permitted access. Keep the customer-to-reseller relationship visible while agreeing a separate method for message-history transfer.

Do not assume portable password hashes, mail filters, forwarding rules, certificates or account paths. Reissue or install eligible SSL through the supported target process and verify coverage. Keep external registrar and DNS authority clear.

Use the shared cutover checklist.

Verify the target application and services, agree final synchronization, then change traffic with a recovery decision already prepared. Retain the source until preservation and recovery requirements are satisfied.