Tutorial · Updated October 2026

Transferring digital asset ownership safely

Prepare a documented handover of code, domains, customer obligations, and infrastructure.

Agree the handover inventory

List repositories, domains, databases, cloud services, analytics, support tools, designs, and third-party licenses.
Record recurring costs, dependencies, access owners, backups, and renewal dates.
Agree the transfer sequence, acceptance checks, transition support, and payment arrangements in writing. SellMyWeb does not hold acquisition funds in escrow.

Review each provider’s ownership-transfer process before committing. Some accounts or licenses cannot be transferred.
For domains, check registrar locks, eligibility, expiry, and authorization-code requirements. Preserve DNS records and mail delivery during the transfer.
Do not assume a payment account can be handed over with its password. Ask the provider about the legal entity and ownership change.

Take recoverable backups and document deployment, rollback, and recovery steps.
Transfer repository and service ownership using provider-supported methods, then verify the buyer can deploy, restore backups, and manage billing.
Give the buyer their own access. After acceptance, rotate credentials, revoke obsolete access, and record who now controls each asset.
Transfer customer data only under the applicable contracts and privacy obligations. Document any required customer notices.

Use these guides as a starting point for your transaction checks. Provider requirements and the facts of each business determine the final handover.