Multi-registrar domain management

Multi-registrar portfolios are normal. The failure mode is managing them as if each registrar UI were a complete system of record.

Why portfolios fragment

• Price shopping on registrations and renewals
• Client-owned accounts you must not migrate
• Historical purchases across years
• Regional accounts (EU vs US billing)

Fighting fragmentation with “transfer everything” projects often stalls. Prefer unified visibility.

Operating model

1. Catalog connections — every registrar login is a named connection.
2. Central inventory — one board with registrar + connection label on each domain.
3. Sync or import — keep expiry/cost fresh.
4. Risk filters — expiring soon, auto-renew off, unlabeled orphans.
5. Decision cadence — renew/drop in one place, execute at the registrar second.

Connection labeling (non-negotiable)

If you have two GoDaddy accounts, “GoDaddy” is not enough. Use labels like:

• GoDaddy — Personal
• GoDaddy — Client Acme
• Namecheap — Investments

DomainsBoard requires a label on every registrar connection for this reason.

Sync order of operations

1. Connect the registrar with the most production domains.
2. Verify a sample of expiry dates against the registrar UI.
3. Add secondary accounts.
4. Keep CSV import for one-off lists that will never have API access.

See the registrar sync pillar and provider guides under that cluster.

Agency pattern

Agencies should label by client and never mix personal speculative names into client filters. Continue in agency client domain management.