If you are planning to use a custom domain for your community that is currently in use on another site or change the domain for your currently published and launched Gradual community, there are specific instructions and processes that need to be followed.
This resource summarizes the process for updating your live community domain or migrating a live community domain along with common pitfalls and tips for a smooth transition.
Domain migration of a live community domain is not self-service. This needs to be closely coordinated with the Gradual team with at least 5 business days of lead time. Please reach out to [email protected] to coordinate a migration.
Migrating a domain currently in use on another platform
Many customers migrating to Gradual want to maintain their current domain for their community. This is easily supported with Gradual and just takes a little bit of coordination with our teams to ensure a smooth transition.
The setup process for an existing domain is similar to a net-new domain, the only difference is the domain change needs to be timed to ensure minimal downtime for users.
Domain migration will follow the same steps outlined in our using a custom domain resource, however the following process should be followed:
Notify the Gradual team at least 5 business days prior to your intended domain switch. This will ensure we can have our engineering team available to help make the change.
Coordinate a specific time (~30 minute window) when you would like the domain change to happen. We typically conduct domain changes during normal support hours between 6am and 6pm PT. It is possible to coordinate a change outside this time window in special circumstances.
Domain change process
You update your DNS records to add a CNAME record pointing your desired to domain to
ingress.gradual.us.Gradual verifies the DNS configuration.
Gradual runs a process to point your domain to your Gradual community.
You and Gradual verify the configuration is correct.
Additional considerations when migrating an existing domain
You may have custom URLs or links that need to be maintained. This can be done using the URL Redirect feature in your dashboard. Simply enter the previous URL and the new destination and these will be redirected automatically.
If migrating existing content or other resources as part of a migration project, it is possible for us to backfill a large volume of redirects to ensure links with high SEO performance are maintained.
Updating your live Gradual community domain
Occasionally it's necessary to update the domain on your current Gradual community. If your community is already live and published and you're changing the domain, there are special considerations to take into account when planning the change.
Preparation for the domain switch:
Notify the Gradual team at least 5 business days prior to your intended domain switch. This will ensure we can have our engineering team available to help make the change.
Coordinate a specific time (~30 minute window) when you would like the domain change to happen. We typically conduct domain changes during normal support hours between 6am and 6pm PT. It is possible to coordinate a change outside this time window in special circumstances.
Domain change process
You update your DNS records to add a CNAME record pointing your new to domain to
ingress.gradual.us.Gradual verifies the DNS configuration.
Gradual runs a process to point your domain to your Gradual community (At this point, your previous community domain will stop working and will result in a Gradual 404 page).
You and Gradual verify the new domain is working.
You update your DNS settings to redirect (typically a 301 redirect) your previous domain to your new domain (this will ensure any traffic to the old domain will still point to your community and the correct page).
You and Gradual verify the configuration is correct.
Additional updates following a domain change
Not all of these changes are necessary for every community, but the following list are common changes or updates that need to be done concurrently when making a domain change
Update SSO Callback URLs: lf your community is configured with SSO for front-end login, the callback URLs in your SSO tool need to updated to the new domain. Note: this does not apply to dashboard SSO, however it will change the "community url" your admins use to log in to your dashboard.
Update LinkedIn Login Callback URLs: If you use LinkedIn Login, you will need to add the new community URLs to your login application in LinkedIn.
Update community email senders: If applicable, you'll also need to update the email sender in your community. This won't impact login or the ability to access the page, but it's best practice to keep these consistent.
Captcha update: If your community has a recaptcha configured at login, the Gradual team will update your Captcha configuration to work with your new domain.
Domain allowlists: Often times a domain migration is due to a company update or change where the email domains for users may change as well. If using the domain allowlist feature for sign-up, make sure the list is updated with the correct domain.
User email updates: Email changes in Gradual require our team to support. If your domain change is due to a company domain change and your teams' emails need to be updated, please inform the Gradual team and we can help make this change for you.
The most important part of a successful domain update or migration is communication. Please be sure to communicate often and well in advance with the Gradual team so we can support your successful transition. Any questions please reach out to [email protected].