Move a domain to another project

You bought a domain for one store, then the product moved to another project in your organization. Handing the domain over used to mean deleting it, adding it again in the other project and waiting for DNS and SSL to validate all over again.

The enemy is a domain tied to the project you first added it to.

On the Domains list, the row menu now has Move to another project. The target can be any project in the same organization. Projects outside an organization can only move domains between projects with the same owner, and you need permission to manage domains in both. DNS, SSL and the validated status carry over, so there is nothing to re-verify and the domain stays live.

Review changes shows what in the current project stops using the domain before anything happens: funnel links, blogs, courses, the courses domain setting and tracking scripts. If the domain's merchant belongs to the current project, the domain arrives without one and you pick a merchant in the new project.

Pages on the domain stay behind in the current project without a domain. Turn on Move all assigned pages to bring them along, which runs in the background. A move without pages switches over right away.

Try it: open Domains, open the menu on a domain's row and click Move to another project. Pick the Target project and click Review changes.