How to change your Zendesk subdomain: A complete guide for 2026

When your company changes its name, merges with another, or undergoes a rebrand, your Zendesk subdomain might need to change too. It's a significant decision. Unlike updating your logo or email signature, changing your Zendesk subdomain affects every URL, integration, and API connection in your support operation.

This guide walks you through everything you need to know: when to make the change, how to prepare, what breaks (and how you'll fix it), and whether you actually need a subdomain change at all. We'll also look at how our Zendesk AI integration works seamlessly with any subdomain configuration you choose.

What is a Zendesk subdomain and why change it?

Your Zendesk subdomain is the unique identifier in your help desk URL. If your address is yourcompany.zendesk.com, then "yourcompany" is your subdomain. It's how Zendesk routes traffic to your specific account and how customers find your help center. Learn more in Zendesk's official subdomain documentation.

Here are the most common reasons teams change their subdomain:

• Company rebrand Your business changed names and the old subdomain no longer reflects your brand
• Merger or acquisition Two companies combined and need a unified support presence
• Spin-off A division became its own entity and needs separate branding
• Legal requirements Trademark conflicts or other legal issues with the current name

Here's the critical thing to understand: renaming your subdomain takes effect immediately. Your old URL stops working the moment you confirm the change. Zendesk can't set up redirects on your behalf. Anyone with bookmarks, email templates, or documentation containing your old URL will hit a dead end.

That's why preparation matters so much. The actual rename takes seconds. The work is in everything that comes before and after.

Subdomain change vs host mapping: Which do you need?

Before proceeding, make sure you actually need a subdomain rename. Many teams confuse this with host mapping, and choosing the wrong approach creates unnecessary work.

Subdomain rename changes your actual Zendesk address. If you're at oldcompany.zendesk.com and rename to newcompany, your new address becomes newcompany.zendesk.com. This is an internal change that'll affect your entire Zendesk instance.

Host mapping keeps your original Zendesk subdomain but shows customers a custom domain. Your help center appears at support.yourcompany.com while your agents still use yourcompany.zendesk.com internally. This only affects what customers see, not how your account functions.

Here's how to decide:

Zendesk strongly recommends host mapping as the first alternative to consider. It gives you the professional branding without breaking integrations, changing email addresses, or requiring extensive post-change cleanup.

If host mapping sounds like it might solve your problem, our complete guide to Zendesk brand host mapping walks through the entire setup process.

Prerequisites and important considerations

A subdomain rename affects nearly every aspect of your Zendesk setup, so it's worth understanding what you're signing up for. You'll want to know exactly what breaks and how you'll fix it.

Requirements

• You must be the account owner. Administrators can't rename subdomains.
• You can't rename sandbox account subdomains.
• Your new subdomain must be 3-63 characters, containing only letters A-Z, numbers 0-9, and dashes. No underscores or special characters.

What breaks and needs fixing

Email addresses change immediately. If you use support@oldcompany.zendesk.com, it becomes support@newcompany.zendesk.com. External forwarding rules must be updated.

Chat becomes inaccessible for up to 2 hours. You'll want to plan this change during low-volume periods.

API endpoints change. Any external systems using your Zendesk API will need to update their URLs from oldcompany.zendesk.com/api/v2/... to newcompany.zendesk.com/api/v2/....

Integrations need reconnection:

• Jira: Disable before the change, then re-enable after
• Salesforce: Disconnect before, then reconnect after
• Sunshine Conversations: You'll need to delete and recreate this entirely
• Authenticated SMTP Connector: Deprecate before, then re-add after

SSO breaks until you reconfigure it. Both SAML and JWT configurations reference your subdomain in the Access Consumer URL.

Ticket sharing agreements must be recreated. Any active sharing agreements with other Zendesk accounts will need to be deactivated and set up again.

Historical ticket limitations. You can't copy and paste comments or images from tickets created before the rename. Attachments in old tickets can't be retrieved through copy/paste.

Early access programs (EAPs) tied to your subdomain will be lost. You'll need to reapply with your new subdomain.

Step-by-step guide to renaming your subdomain

If you've weighed the considerations and decided to proceed, here's exactly what you'll do.

Step 1: Pre-change preparation

Start by documenting your current setup. You'll need this reference during the cleanup phase. Here's what to capture:

• List all external email forwarding rules pointing to your current subdomain
• Identify all integrations in Admin Center > Apps > Channel apps
• Document API endpoints used by external systems
• Note any SSO configurations (SAML or JWT)
• Record active ticket sharing agreements
• Check if you have any EAP access tied to your subdomain

Now you'll prepare the changes:

1. Update email forwarding rules at your domain registrar to point to your new subdomain address
2. Disable the Jira integration in Admin Center > Apps > Channel apps
3. Disconnect Salesforce integration if it's connected
4. Notify your team of the planned downtime window
5. Schedule the change during your lowest support volume hours

Step 2: Rename the subdomain

This is the actual change. It takes seconds but has immediate effect. Here's what you'll do:

1. Go to Admin Center > Account > Appearance > Branding
2. In the Subdomain section, click the Brands menu
3. Click the options menu next to your brand, then select Edit
4. Enter your new subdomain name
5. Click Save
6. Review the warning about consequences, then click Yes, change subdomain

The change is immediate. Your old URL won't work anymore.

Step 3: Post-change tasks

Now the cleanup work begins. You'll work through this checklist:

Integrations:

• Re-enable Jira integration
• Reconnect Salesforce
• Update Web Widget code on your website (get new code from Admin Center > Channels > Classic > Web Widget)
• Update Mobile SDK configuration with new subdomain
• Reconfigure SSO with new Access Consumer URL

External systems:

• Update API endpoints in all external systems
• Refresh API tokens if needed
• Update webhook URLs

Zendesk-specific:

• Recreate ticket sharing agreements
• Update workforce management (WFM) subdomain if applicable
• Update status notification subscriptions

Communication:

• Notify customers of new support email addresses
• Update email templates and signatures
• Revise help center articles mentioning the old URL
• Update any marketing materials or documentation

Common issues and troubleshooting

Even with careful preparation, things can go wrong. Here's what you'll want to watch for:

SSL certificate errors. If you use host mapping with SSL, you'll need to update or regenerate your certificate for the new subdomain.

Email forwarding delays. DNS propagation can take hours. If emails aren't routing correctly, verify your forwarding rules and allow time for DNS updates.

Chat widget still shows old subdomain. Clear your browser cache and verify you're using the updated widget code from your new subdomain.

API calls returning 401 errors. Check that you've updated both the endpoint URL and any authentication tokens that might be subdomain-specific.

SSO login loops. The Access Consumer URL in your SSO configuration must exactly match your new subdomain. Even a small typo here causes authentication failures.

Missing images in old tickets. This is expected behavior. You'll want to contact Zendesk Support if you need assistance with specific attachments.

Integration authentication failures. OAuth-based integrations often need re-authorization after subdomain changes. Disconnect completely and reconnect fresh.

When to consider host mapping instead

If this process sounds overwhelming, host mapping might be the better choice. It gives you professional branding without the operational headache.

With host mapping, you'll keep your existing Zendesk subdomain internally. Your agents continue using yourcompany.zendesk.com. Customers see support.yourcompany.com or help.yourcompany.com.

The benefits are significant:

• No integration breaks
• No API endpoint changes
• No email address changes
• No downtime
• No post-change cleanup

You get the professional appearance without touching any of your backend systems.

Setting up host mapping involves creating a CNAME record with your DNS provider and configuring SSL certificates in Zendesk. The entire process typically takes under an hour, most of which is waiting for DNS propagation.

If you're managing multiple brands in Zendesk, host mapping becomes even more valuable. Each brand can have its own custom domain without the complexity of multiple subdomain renames.

Our Zendesk AI agent works seamlessly with host-mapped domains, providing consistent AI-powered support regardless of which URL your customers use to reach you.

Planning your Zendesk subdomain change

If you've decided a subdomain rename is necessary, treat it as a small project. Create a timeline with specific owners for each integration update. Test what you can in a sandbox environment first. You'll want to communicate the change to customers well in advance, especially if your support email address will change.

The key is preparation. The actual rename takes seconds. The work is in the before and after. Get your checklist in order, schedule during low-volume hours, and have your team ready to handle the post-change cleanup.

Remember: if you're primarily concerned about customer-facing branding, host mapping solves that problem without any of the operational disruption.

If you're looking to enhance your Zendesk setup beyond URL configuration, our AI-powered support tools integrate seamlessly with both standard and host-mapped Zendesk instances. Check out our pricing to see how AI assistance can complement your support operations.