Skip to content
Talk to us

Zendesk migration

Summarise with AI

Ask your AI about this page

Opens in a new tab with a ready-made prompt about this page.

Zendesk migration, with every ticket and article intact.

Move to Zendesk from Intercom, Freshdesk, Salesforce, HubSpot, Help Scout or Jira, or merge two Zendesks into one. Your history, contacts, help centre and integrations come across, checked by a person before you switch.

  • Full history: tickets, contacts, articles
  • A test migration you check first
  • No downtime at cutover
  • Fixed price, live in 4 to 6 weeks
Zendesk Premier Partner

★ 5.0Zendesk Marketplace

150+Zendesk implementations

Run by ex-Zendesk people

Into Zendesk, from

The paths we deliver every month

7 paths
  • Intercom
  • Freshdesk
  • Salesforce
  • HubSpot
  • Help Scout
  • Jira
Zendesk
Plus Zendesk to Zendesk, when two instances become one.

Our customers

Trusted by 150+ support teams to move to Zendesk

From one inbox to three markets, teams who moved to Zendesk with us say it went smoothly. Here is what they say.

Sydney Opera House, MYOB,
Pandora and many more
5.0
Zendesk Marketplace
mycarEzypayEMU AustraliaMYOBSydney Opera HousePandoraMontuLovisa

Migration paths

Where are you moving from? Start there.

  • Intercom to Zendesk

    Conversations become tickets, without losing context, and Operator bots become Zendesk AI agents.

    • Conversations
    • Contacts
    • Articles
    • Workflows
  • Freshdesk to Zendesk

    One of the cleanest moves: Freshdesk’s automation model is close to Zendesk’s.

    • Tickets
    • Agents and groups
    • SLAs
    • Custom fields
  • Salesforce Service Cloud to Zendesk

    Redesigned, not lifted and shifted: over-customised routing gets simpler on the way.

    • Cases
    • Accounts
    • Knowledge
    • Routing
  • HubSpot Service Hub to Zendesk

    Support moves to Zendesk; HubSpot can stay your CRM, connected natively.

    • Tickets
    • Contacts
    • Knowledge base
  • Help Scout to Zendesk

    A small, clean data model that lifts across quickly.

    • Conversations
    • Customers
    • Mailboxes
    • Saved replies
  • Jira Service Management to Zendesk

    Customer-facing support moves to Zendesk; Jira stays for engineering, synced both ways.

    • Issues
    • Queues
    • Forms
    • Jira sync
  • Zendesk to Zendesk

    Two instances merged into one, with multi-brand done properly.

    • Tickets
    • Agents
    • Macros
    • Help centres
  • Only the help centre?

    Articles, categories and search redirects, with your SEO kept by proper 301 redirects.

    • Articles
    • Categories
    • 301 redirects

What we carry across

Everything your team relies on, moved and mapped.

  • Tickets and history

    Every conversation, attachment and custom field, searchable in Zendesk.

  • Contacts and accounts

    Customers and organisations, with their custom fields and segments.

  • Workflows

    Macros, triggers, automations and SLAs, rebuilt as Zendesk equivalents.

  • Help centre and integrations

    Articles and structure moved, design kept or rebuilt, integrations rewired.

How a migration runs

Checked by a person, at every step.

We don’t hand you a self-serve tool and walk away. With Zendesk’s import APIs, partner-grade tools like Help Desk Migration, custom scripts where needed and our own audit, every migration is validated end to end.

  1. Step 1

    Map

    Your old platform mapped field by field to Zendesk’s model, with what to keep, merge or leave behind.

    You getA mapping you sign off.

  2. Step 2

    Test migration

    A sample of your data moved first, for your team to check in Zendesk before anything final.

    You getNo surprises on the day.

  3. Step 3

    Migrate and cut over

    The full move, then a final sync of anything new, so support never stops.

    You getNo downtime.

  4. Step 4

    Validate

    Counts and samples checked against the source by our audit, before the old platform goes.

    You getProof nothing was lost.

Questions

Before you migrate

How long does a Zendesk migration take?

A migration runs inside a Zendesk Implementation: most teams are live in 4 to 6 weeks, and the data move itself takes one to two weeks of that.

Will we lose any ticket history?

No. Tickets, conversations, attachments and custom fields come across and stay searchable in Zendesk. We check counts and samples against your old platform before it’s switched off.

Is there downtime when we switch?

No. We migrate, then run a final sync of anything new just before cutover, so your team keeps answering customers throughout.

Can you migrate only our help centre?

Yes. Articles, categories and attachments move to Zendesk’s help centre, and 301 redirects keep the search rankings your old articles earned.

We’re a large organisation. Where do we start?

With our guide to Zendesk migration strategies for large organisations: phasing, data mapping and running two systems side by side. Then book a scoping call and we’ll map yours.

Book a call

Migrating to Zendesk? Let’s map it.


We’ll map your current platform, scope the migration and give you a fixed price.

You will get a calendar invite with a video link straight away.

  1. A call about your platform, your data and your timing.
  2. The migration mapped and scoped.
  3. A fixed price and a written plan.

Who you might be speaking with

Hugo Richard

Hugo Richard

Head of Growth, ex Zendesk

Chad Susa

Chad Susa

Founder, Head of Service, ex Zendesk

Meet with the Gravity team

Book a migration scoping call
One of a few Premier Partners in ANZZendesk Implementation Partner★ 5.0Rated on the Zendesk Marketplace8 appsBuilt by us, live on the Zendesk Marketplace150+Zendesk implementations