How do I migrate my domain to the new version without taking the site down?
Click Migrate to the new version, create the TXT records and wait for the certificate step to show Done. Only then switch the CNAME to domains.clickmax.space. In that order, the site never goes down.
Before you start
- Role: workspace Owner or Admin.
- You need access to the DNS panel of the provider where the domain is registered.
- The New version available notice, with the Migrate to the new version button, shows on the details of a domain on the previous version, the screen without the steps card (Connect the domain in 3 steps, Finish the migration in 3 steps or All set!). If one of those cards is already there, the domain is already on the new version and there is nothing to migrate.
- Once migrated, the domain cannot go back to the previous version.
1. Click Migrate to the new version
- Open Domains and click the pencil on the domain's row.
- Click Migrate to the new version.
The site stays up on its current connection and the domain's status does not change: it stays Connected, with a Migrating badge next to it, and the status help says "Follow the steps below to finish the migration." The Finish the migration in 3 steps card appears, with a progress bar and the count X of 3 done:
- Create the TXT record that confirms the domain is yours — with the note "Do not change the CNAME yet: the site stays online."
- Create the TXT record for the security certificate (HTTPS).
- Change the CNAME to domains.clickmax.space.
Each step shows a badge: Done, In progress, Your action or Waiting. The TXT records only exist in the migration: they activate the security certificate before you switch the CNAME. The Recheck button sits in the card's footer.
2. Create only the TXT records
In your provider's panel, create the TXT records from steps 1 and 2. Copy the Name and Value with the copy buttons on screen: the values are unique to your domain.
- Do not change the CNAME yet. It is what keeps the site up while the new certificate is issued. Step 3 stays Waiting, with the warning "Change the CNAME only after the certificate is active. Until then the site would lose HTTPS."
- The
_acme-challengeTXT shows up a few seconds after you click Migrate to the new version. Click Recheck to refresh the list. - The value of the
_acme-challengeTXT can change after the domain is confirmed. The screen warns about it under the record: "This value can change after the domain is confirmed. If it changes, update the record at your provider." Once step 1 shows Done, compare the value on screen with the one at your provider and, if it changed, update the record. - The
_acme-challengeTXT can come as more than one record, with the same name and different values. The screen warns about it and numbers each one, for example (1 of 2) and (2 of 2): create all of them, because the certificate is only issued once all are published. One does not replace the other. - Each record's Name already comes the way most providers ask for it: only what comes before the domain, for example
_cf-custom-hostname.wwwand_acme-challenge.www. If your provider asks for the full name, use the one shown right below each record. - During the migration, the Rather not touch the DNS? box, with the Set up automatically button, only shows once the certificate is active, because it writes all the records at once, the CNAME included. So create the TXT records by hand.
3. When step 2 shows Done, switch the CNAME
Click Recheck every now and then to refresh the screen. Once the certificate is active, step 2 shows Done and the _acme-challenge TXT is no longer shown. Step 3 turns into Your action: then the CNAME can change.
If step 1 already shows Done and step 2 does not, check whether the value of the _acme-challenge TXT on screen has changed. If it has, copy the new value and update the record at your provider.
At your provider, edit the domain's CNAME, which currently points to entri-domains.clickmax.space, and change its value to domains.clickmax.space. The record's name stays the same. From this point the Rather not touch the DNS? box shows in step 3, and its Set up automatically button can make the switch for you with supported providers.
If the CNAME changes before step 2 shows Done, the site's HTTPS goes down until the certificate is issued. If that already happened, keep the TXT records at your provider and click Recheck until the step shows Done.
4. Click Recheck
After switching the CNAME, click Recheck. Once the new CNAME is recognised, the migration is done, the site never went down, and the steps give way to the All set!
If the domain was not Connected
If the domain was not Connected before you migrated (for example, it was Disconnected), there is no live site to protect. The screen shows Connect the domain in 3 steps with the same three records (TXT, TXT and Create the CNAME record at your provider). Create all three at once, the CNAME to domains.clickmax.space included, and click Recheck. The value of the _acme-challenge TXT can change after the domain is confirmed: if the certificate does not activate, check the value on screen and update it at your provider. What each status means is in connect a domain you already own.
Related
If it didn't work
- The certificate step never shows Done: check that all the TXT records are at your provider with the exact name and value from the screen. The value of the
_acme-challengeTXT may have changed after the domain was confirmed; if it did, update it and click Recheck — see my domain does not open. - The CNAME was switched too early and the site has no HTTPS: keep the TXT records and click Recheck until the certificate step shows Done. HTTPS comes back once the certificate is issued.
- The Migrate to the new version button is missing and the domain has the Older version badge: it is still on the older page builder. First see how to migrate domains from the older builder.