Selling a portfolio domain: an operational handoff checklist

When should a sold domain leave the active portfolio?

Record the sale decision when it occurs, but distinguish it from completed delivery. Keep the holding in a pending-handoff state until the agreed delivery process and the relevant registrar evidence support completion. An accepted offer, payment event, and domain transfer are separate records.

This checklist is part of the portfolio management guide. It addresses operational records, not domain valuation, escrow advice, or a promise that AIvikings supplies a marketplace or settlement service.

Confirm the delivery route before changing the domain

Identify the exact name, the account currently controlling it, the recipient, and the delivery method agreed through the transaction's own process. Different registrar and transaction arrangements can require different steps.

Do not assume that a registrar transfer, an internal account move, and a registrant-contact change are interchangeable. Confirm which operations the actual registrar supports and what evidence establishes completion. The portfolio transfer checklist covers readiness and verification when a registrar transfer is the chosen route.

Assign one operator to the handoff and preserve the transaction reference in your business records. Avoid competing instructions from multiple spreadsheets or separate assistant sessions.

Protect the information needed for delivery

Use the supported, authorized account workflow to retrieve any required transfer code. Treat it as a secret, not as an ordinary note in a public sales sheet or shared article. Restrict who can access it and follow the chosen transaction process for communicating it.

Record that a code was obtained or delivered without copying its value into every work log. A business reference lets another operator locate the protected record while limiting exposure.

Check transfer readiness before scheduling the handoff. Locks, status, timing, or pending account work can affect which next step is possible. Preserve those exceptions and seek the correct registrar guidance rather than guessing at a universal release procedure.

Keep DNS and services separate from the ownership task

A domain may still carry email, a landing page, or another service during the handoff. Record what must remain working and which configuration changes are actually authorized.

Do not replace nameservers solely because the commercial record says sold. A transfer can be a separate operation from DNS migration. Where delegation must change, use the nameserver-change checklist to preserve the current state, prepare the destination, and verify the result.

Likewise, a completed registrar action is not evidence that a buyer's website or email is ready. Keep completion statements specific to the stage you verified.

What should the handoff ledger show?

Keep the domain, source account, transaction reference, requested delivery action, attempt time, result, and outstanding conditions. Store the actual supporting evidence where your access and retention process allows it.

Useful states include delivery not started, delivery attempted, waiting on another party, confirmed, and unknown. These are your operating states, not invented names for registrar API responses.

For multiple names, retain a per-domain result. One completed transfer should not make an entire bundle appear delivered. An unresolved domain still needs an owner and next step even if the commercial agreement covers all names together.

How should you update the portfolio afterward?

Once the relevant completion conditions are met, update the inventory and retain the historical acquisition and disposal references. Reconcile the account view with the delivery record; do not delete a conflicting row merely to make the counts agree.

Review any future renewal instructions attached to the holding through the supported account process. A spreadsheet change alone does not change registrar settings. Preserve the distinction between a completed delivery and any billing or account cleanup that remains.

If an outcome is uncertain, investigate account state before repeating a sensitive operation. The same evidence-first approach applies to acquisitions and to the renewal review queue.