Zendesk migration
Moving off Zendesk?
We handle the migration. Tickets, contacts, KB articles, custom fields and attachments move to your new platform while your team keeps working.
Scope my migrationFree sample migration of 100 of your records, plus a flexible quote within 24 hours.
- 1000+migrations
- 15 yearsof collective experience
- SOC 2 Type IIaudited controls
Migration paths
Where can I move from Zendesk?
Routes we run from Zendesk. Open a route to see what migrates, or ask us about one that is not listed yet.
What moves
What moves from Zendesk?
The objects we carry across by default. Your exact scope is agreed on the scoping call. Open a data type to see which fields migrate.
- Tickets
- Contacts
- Organizations
- KB Articles
- Attachments
- Custom Fields
- Tags
- Comments
Help Desk
Agents7 fields
- Name
- Role
- Group membership
- Agent mapping & reassignment
- Auto-create missing agents
- Handle deleted/inactive agents
Customers9 fields
- ID
- Name
- Phone
- Company
- Details
- Language
- Time zone
- Custom fields
Organizations5 fields
- ID
- Name
- Description
- Domains
- Custom fields
Tickets30 fields
- ID
- Subject
- Tags
- Company
- External ID
- Group
- Source
- Status
- CC
- Staff
- Contact
- Comments
- Comment author
- Comment privacy
- Comment publicity
- Comment body
- Comment attachments
- Comment recording
- Comment created date
- Conversations
- Created date
- Updated date
- Closed date
- Brand
- Form
- Custom status
- Type
- Priority
- Due date
- Custom fields
Knowledge Base
Categories4 fields
- Name
- Description
- Position
- Translations
Sections5 fields
- Name
- Description
- Position
- Category mapping
- Translations
Articles11 fields
- Title
- Body
- Position
- Author
- Status
- Tags
- Redirects
- Translations
- Attachments
- User segments
- Permission groups
Business Rules
Macros7 fields
- Agents
- Name
- Status
- Dynamic action fields
- Contacts
- Companies
- Tickets
Triggers7 fields
- Agents
- Name
- Status
- Dynamic action fields
- Contacts
- Companies
- Tickets
How it works
A specialist team runs your migration,from scoping call to sign-off.
01 · Scope
We map every field with you
A scoping call with an ITSM specialist. Fields, rules and exceptions agreed before anything moves.
02 · Sample
Check 100 of your own records first
We move 100 records you choose into your new platform. Your team checks them. Then a flexible quote within 24 hours.
03 · Migrate
The rest moves, with a final sync at cutover
Our engineers run the migration and sync any last changes at cutover, so your team keeps working.
04 · Reconcile
Every record counted, every exception closed
A reconciliation report counts every record from source to destination. Anything that did not fit is fixed and shown to you before sign-off.
Migration scenarios
How are you moving off Zendesk?
Every migration is different. We handle all three.
Full migration
Move everything: tickets, contacts, KB articles, custom fields and attachments. Your complete history lands in the new platform.
For example: A support team switching platforms at renewal.
Merge multiple instances
Consolidate separate instances into one environment. We handle deduplication and field conflicts.
For example: Post-acquisition teams merging two accounts into one.
Partial migration
Filter by date range, ticket status, tags or any criteria. Move only what matters and leave the rest behind.
For example: Only open tickets and the last 12 months of history.
Zendesk migration questions
Still unsure? Ask us on the scoping call.
What happens to side conversations?
Side conversations come over as private comments on the parent ticket. The content, timestamps and participants are preserved.
Can I migrate just closed tickets?
Yes. We can filter by status, date range, tags or any combination. You control exactly what moves.
What about our macros and triggers?
Macros and triggers are documented and mapped to the equivalent in your target platform. We review the mapping with your team before running it.
Will our KB article URLs break?
We can set up redirects from old article URLs to the new ones, so bookmarked links keep working.
How do you handle custom fields?
We map every custom field type (text, dropdown, checkbox, date, number) to its equivalent in the target platform. Fields without a direct match are converted to the closest type with your approval.
What if we have multiple Zendesk brands?
We can migrate all brands into one environment or keep them separate. Multi-brand migrations are one of our most common scenarios.
How long does a Zendesk migration take?
It depends on data volume. Small instances (under 10,000 tickets) can finish in hours; larger ones take a few days. The free sample migration shows you the timeline before you commit.
Is there downtime during the migration?
Zendesk stays fully operational during the main run. We use delta sync to pick up anything that changes while the migration runs, then switch over in one planned window.
What about call recordings and attachments?
Call recordings transfer as attachments on the ticket. File attachments, inline images and embedded content are migrated with their original timestamps and associations.
Can we test the migration before going live?
Yes. Every migration starts with a free sample migration of 100 of your own records. You review the results and the field mappings before we touch production.
How do you handle deleted or suspended agents?
We can create missing agents in the target platform, map them to existing agents, or reassign their tickets. You choose the approach on the scoping call.
What does it cost?
Pricing is per record and depends on your platforms and what moves. After the scoping call and the sample, you get a flexible quote within 24 hours.

Start with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a flexible quote within 24 hours.