How Do You Change a Zendesk Subdomain Without Losing Data?

You change a Zendesk subdomain as the account owner in Admin Center under Account > Appearance > Branding, by clicking "Change your subdomain", and no ticket, user, organization, group, trigger or automation is lost. The risk is links, not data: Zendesk says it "cannot set up a redirect on your behalf", so every link to the old myolddomain.zendesk.com address stops working the moment you rename. If you only want customers to see a branded URL, Zendesk recommends host mapping instead, which leaves the account address alone.

What happens to your tickets when you change the subdomain?

Nothing. Solved, open and archived tickets all stay, and so does everything around them. Zendesk's own documentation puts it this way:

"All your existing users, tickets, organizations, and groups will automatically exist at your new URL. Additionally, your triggers and automations will be all set."

User profiles and ticket histories stay intact too, although every user has to sign in again at the new address. Your agents keep full access to the ticket history, and customer data doesn't move anywhere.

Why do links break after a subdomain change?

Zendesk doesn't redirect the old subdomain, and it can't set one up for you, so any link that points to the old address returns an error from the moment you rename. Think about where your old subdomain is written down:

• Email notifications already sent to customers with ticket links
• Bookmarks your agents have saved
• Internal documentation with links to specific tickets
• Old knowledge base articles with embedded ticket references
• Third-party integrations that point to your Zendesk URL

Each of these stops working at the switch. That makes the rename more of a communication job than a technical one, so give your team and your users notice well before the change.

Should you create a new brand instead of renaming?

No. It's tempting to create a new brand with the new subdomain and make it the default, but it makes things worse. You can run multiple brands in Zendesk, each with its own subdomain, but tickets belong to a brand. Your existing tickets stay on the original brand and its subdomain.

That split causes four problems:

• Agent workflow confusion: agents need access to both brands to see all tickets
• Split ticket history: historical data is divided between two brands
• Messier reporting: you pull reports across multiple brands
• The link issue persists: old links still point to the original brand's subdomain

The official rename is the only clean way to change the account address itself.

How do you rename a Zendesk subdomain step by step?

Who is allowed to do it?

Only the account owner can rename a subdomain. If that isn't you, find the account owner and ask them to make the change, or contact Zendesk Customer Support if the owner is no longer reachable.

Step-by-step process

1. Pick a low-traffic window

Schedule the change for off-peak hours or a weekend. Chat can be unavailable for up to 2 hours afterward, and the rename halts all Zendesk bot and autoreply activity, so you want as few customers waiting as possible.

2. Update these before you rename

• Email forwarding to your support addresses
• CNAME records and SSL certificates, if you use host mapping
• Jira integration (disable it, rename, then re-enable)
• Salesforce integration (disconnect it first)

3. Make the change

In Admin Center, go to Account > Appearance > Branding and click "Change your subdomain" in the Subdomain field. If you run multiple brands, the subdomain sits under Account > Brand management > Brands instead. Enter the new subdomain, confirm, and refresh your browser to see the change.

4. Update these after you rename

• Support email addresses: the default address works straight away, but there may be a delay of several hours before you can add new native support addresses
• Web Widget and messaging script: paste the new code on every page that embeds it, and update any Mobile SDK code
• Ticket sharing agreements: deactivate and recreate them; sharing on individual tickets also stops working
• API endpoints: update any script or integration that calls the old subdomain
• Single sign-on: update SAML or JWT settings that reference the old address
• Salesforce: reconnect the integration you disconnected
• Third-party integrations: review anything else that stores your Zendesk URL

What else changes on the day?

Users have to sign in again at the new address, though their profiles and ticket histories stay intact. Chat may be inaccessible for up to 2 hours, and bots and autoreplies stop until you check them.

Is host mapping a better alternative to renaming?

For most teams, yes. Zendesk's documentation says host mapping "is highly recommended as an alternative to renaming your subdomain." Host mapping changes only the external-facing URL of your help center. It doesn't change the sign-in page or the agent interface, which stay on your Zendesk address.

What is host mapping?

Host mapping lets customers reach your help center at your own domain, such as support.yourcompany.com, while the Zendesk account address stays the same. That means:

• No broken agent links: the agent interface URL doesn't change
• A branded address: customers see your domain
• Reversible: you can change the customer-facing URL later without touching the account
• No rename side effects: chat, bots and sign-ins carry on as before

How do you set up host mapping?

Create a CNAME record at your domain registrar that points your chosen subdomain to your Zendesk address, then enter the new address in Admin Center under Account > Appearance > Branding (or under Brand management for multiple brands). DNS changes take anywhere from a few hours to a day to propagate, depending on your TTL. For SSL, Zendesk recommends its free, automatically renewed Let's Encrypt certificate, which covers up to 100 host-mapped domains; you can upload your own certificate instead, but Zendesk won't renew it for you.

You get a branded URL for customers while the internal setup stays exactly as it was.

What other risks come with a subdomain change?

Early access programs

Access to many early access programs (EAPs) is controlled by account subdomain. After a rename you lose access to those EAPs and have to sign up again under the new subdomain.

Copying old comments and images

After the change, you can't copy and paste comments (internal or public) or images from tickets created under the old domain. Pasted content arrives with broken images and incomplete comments, so recreate the comment or re-upload the attachment directly in the new domain.

How should you tell your team and customers?

Whether you rename or use host mapping, communication decides how smooth it goes.

1. Notify your team

• Give at least 1-2 weeks notice
• Explain what's changing and what stays the same
• Share the exact date and time of the change
• Send the new URLs so people can update bookmarks

2. Update your documentation

• Review internal wikis and runbooks
• Replace embedded Zendesk links
• Write a short reference sheet with the new URLs

3. Inform your customers

• Email regular users before the change
• Update support links on your website
• Add a banner to your help center ahead of the switch

4. Prepare your agents

• Walk through the post-change checklist
• Make sure they know they'll need to sign in again
• Remind them that ticket histories stay intact

Which option should you choose?

Choose host mapping if:

• You want a branded customer-facing URL without disrupting operations
• You need existing links and bookmarks to keep working
• You want the freedom to change the customer-facing URL again later

Choose a subdomain rename if:

• You need to change the actual Zendesk account address
• You can live with broken links and handle the communication
• You have time to update every integration, widget and document

Don't create a new brand if:

• Your goal is simply to change your subdomain, because it won't solve the problem

Frequently asked questions

Will I lose tickets if I change my Zendesk subdomain?

No. Users, tickets, organizations, groups, triggers and automations all move to the new URL automatically. What breaks is every link to the old address.

Does Zendesk redirect the old subdomain?

No. Zendesk cannot set up a redirect for you, so bookmarks, emailed ticket links and integrations that use the old address stop working at the switch.

Can Zendesk support rename the subdomain for me?

The account owner makes the change in Admin Center. If you can't reach the owner, Zendesk's documentation points you to Zendesk Customer Support.

Where can you read Zendesk's own documentation?

• Official Zendesk Documentation: Renaming Your Subdomain
• Host Mapping - Changing the URL of Your Help Center
• Setting Up Multiple Brands