To split a Zendesk instance means exporting selected data, such as tickets, users, and help center articles, to a separate account.
The main challenge is data integrity. IT leaders must maintain ticket history and parent-child relationships to protect SLA performance. Because manual exports often lead to fragmented data, teams use the Help Desk Migration Wizard to define scope and test field mappings in a sandbox.
When Splitting a Zendesk Instance Makes Sense
Companies split Zendesk accounts in situations like:
- Acquisitions or divestitures: separate support data when business units change ownership.
- Team restructuring: removing conflicts between triggers, macros, or workflows used by different teams.
- Product-specific support: allowing separate workflows and independent SLAs for different products.
- Brand separation: creating unique CSS/theming, custom SSO, and dedicated customer-facing subdomains.
- Data residency: complying with localized sovereignty laws (e.g., GDPR or CCPA).
- Platform limits: dedicated accounts provide separate sandboxes, unique SSO configurations, and higher API rate limits than shared Multibrand setups.
Step-by-Step Zendesk Instance Splitting Process
Zendesk migration should follow a controlled process. The goal is to move data while keeping the original system stable.
Defining Requirements and Scope
To effectively split Zendesk brands, identify what data and configurations need to move. Typically, that includes:
- Tickets, comments, and attachments
- Users and organizations
- Knowledge base articles and categories
- Triggers, automations, macros, and custom fields
Determine filtering criteria, such as ticket groups, brands, tags, or creation dates, to ensure only relevant data moves. Map dependencies across workflows to avoid broken processes after migration. Next, review shared settings such as ticket fields, triggers, macros, and automations.
Custom Settings and Demo Migration
Request a custom migration to identify problems early. Adjustments can be made before the Full migration. A Demo Migration s a non-negotiable step to split Zendesk brands with precision preview results, verify ticket logic, and adjust field mapping without affecting your live production instance.
Full Migration and Validation
Once the Demo is approved, start the Zendesk data migration to move your bulk data. This final stage requires verifying
- Migrated all filtered tickets, users, organizations, and knowledge base content.
- Parent-child ticket relationships and comment history are preserved.
- Test triggers, macros, automations, and routing rules in the new instance without affecting the original environment.
Split Articles into Multiple Brands (Zendesk Guide)
To split Zendesk Guide set up new help centers, and move articles into their new structures with zero downtime. This requires rebuilding the knowledge base structure and assigning articles to the correct brand.
Create New Brands
To effectively split Zendesk brands, create the required brands in the Brand Management section.
- Go to Admin Center → Account → Brand Management → Brands
- Add a new brand with a unique name and subdomain
- Configure CNAME, SSL, and agent signatures to avoid security warnings at launch.
Activate Guide for Each Brand
Zendesk Guide works on a per-brand basis, so you need to go to Guide > Guide settings. In Guide settings, configure:
- access permissions
- editor roles
- help center visibility
- themes and layouts
How to Split Zendesk Guide Articles
To split Guide data, follow these steps to ensure a clean Zendesk multibrand architecture:
- Identify source and target brand IDs within the Zendesk API to ensure precise data routing.
- Export of Zendesk help center articles, including attachments, inline images, and labels.
- Map your existing categories and sections to the new brand’s structure to export Zendesk Guide data effectively.
- Use Article Multiplacement if the same article must appear in multiple brands to prevent duplication and centralize updates. Run the final Zendesk Guide Import.
Ticket Splitting and Filtering Options
Most migrations do not move every ticket. Instead, administrators define filters to control what is transferred. Running how to split a ticket in Zendesk at an enterprise level requires strict governance.
- Specify exact groups to ensure every Zendesk split ticket migrates with its parent context and custom fields intact.
- When you split ticket Zendesk data, custom rollback logic ensures original parent tickets remain untouched and fully recoverable.
- Run Zendesk split tickets across business units by migrating only relevant, filtered data without risking SLA breaches.
Handling Contacts and Companies
Migrate only the users and organizations associated with your filtered ticket subsets to maintain the integrity of customer relationships across Zendesk instances.
- Automatically map User Identities (email, phone, external ID) to prevent duplicate or "orphan" records.
- Provide agents with immediate access to the full customer history the moment a migrated ticket is opened.
- Filter the migration to exclude unrelated contacts, transferring only the data relevant to the specific business unit.
Next Steps and Support
For mission-critical operations, using a proven Zendesk migration tool eliminates the risks of manual exports and complex edge cases.
- Use the Migration Wizard to map your data and preview the split with a sample set.