Skip to Content
CUSTOM DOMAIN

Migration guide

Switching to Custom Domain

For teams already running a custom-domain integration, on another provider or built in-house, who would rather stop maintaining it. The shape of the problem is the same everywhere, so the migration is mechanical: a competent developer can migrate in an afternoon.

The afternoon, step by step

  1. 01

    Map your domains

    Export the hostnames you serve today and the state each one is in. This list is the whole migration, everything else is running it.

  2. 02

    Create an application

    One API call or a minute in the console. You get your target records and register the webhook endpoint that will confirm each cutover.

  3. 03

    Point CNAMEs to edge.customdomain.ai

    Update the records, or your customer-facing instructions, so each hostname resolves to our edge instead of your old target.

  4. 04

    Verify, certificates issue automatically

    As each hostname verifies, its certificate is issued. No CSRs, no uploads, no per-domain ceremony.

  5. 05

    Flip traffic, webhooks confirm

    Cut over. A webhook per domain tells you it’s live, so the migration script can check itself off.

What carries over

Your domains stay live during the cutover.

A connection verifies before it serves, so nothing is unplugged until its replacement is proven. Your customers keep their domains, their bookmarks, and their HTTPS, the only thing that changes is which system is on the hook at 3 a.m.

Bring your domain list.

Thirty minutes, your migration mapped end to end, hard questions welcome.

Book a migration call Read the docs