Addon to Account
Addon to Account converts one addon domain into a separate hosting account while moving its related website, mail, DNS, SSL, web policy, application metadata, and selected databases.
Where to find it: Open the Server menu and choose Addon to Account. Conditional items appear only when their service is installed and available.
Available to: Root and resellers. A reseller sees only delegated accounts and provider-approved packages or features.
What this page does
Use it when a website that currently shares an account needs its own username, package, owner, quotas, login, and lifecycle. The conversion uses SHM's normal account-creation rules, then moves the domain-specific resources through a tracked job.
Before you start
This is a structural conversion, not a cosmetic rename. Take a current backup, confirm the addon domain and document root, decide which databases and users belong to that site, review mail and cron dependencies, and plan a maintenance window. There is no casual one-click undo after the source and target metadata are committed.
Access and ownership
Root can select any visible addon domain, package, and target owner. A reseller sees only owned accounts; the new account remains owned by that reseller, and the normal reseller package and disk-pool checks apply.
Conversion setup
| Field | What it controls |
|---|---|
| Addon domain | The exact source account, addon id, domain, and document root. |
| New username | The new Linux and SHM account identity; it must pass normal username and uniqueness validation. |
| Contact email | The administrative contact stored for the new account. |
| Target package | Quotas, resources, features, and shell policy for the new account. |
| Owner | Root or a selected reseller; shown to root only. |
Preview is mandatory
Preview validates the source and destination and lists the resources SHM can move. It shows files, mail, DNS, SSL, web settings, application metadata, and candidate MySQL/PostgreSQL databases and users. Select only database items that belong to the converted site; a familiar name is not proof of ownership.
Job behavior
The job creates the target account, copies and reassigns resources in guarded stages, updates ownership and generated configuration, rebuilds source and target runtime state, and records progress. If an idempotent stage stops, Resume continues the recorded job rather than starting a competing conversion.
After conversion
- Open both source and target accounts and confirm the addon no longer appears in the source.
- Test the website, redirects, cache, HTTP Guard, ModSecurity, SSL, mail, cron, applications, and selected databases.
- Verify file ownership and account resource usage.
- Keep the pre-conversion backup until the new account has passed customer acceptance.
How to use it
- Select the addon domain and enter the new account details.
- Run Preview.
- Review every resource and select only the databases and users that should move.
- Resolve all warnings and take a backup.
- Start Conversion once.
- Follow Job Progress; use Resume only when offered.
- Complete the source-and-target verification checklist.
Result and next check
The former addon domain becomes the primary domain of a new standalone SHM account, with the selected resources reassigned and both accounts rebuilt. The job is complete only after source cleanup and target services are independently verified.
Theme color