Skip to content
Get a quote

Helpdesk migration

Move tickets, threads, and customer history between any two helpdesks

Short answer

FlitStack AI migrates tickets, threads, and customer histories between helpdesks: every field mapped and validated, a sample run you approve, then the full migration with history, attachments and associations, and one-click rollback. We also set up the new system's process, not only its data.

Helpdesk migration illustration
What moves✓ Tickets✓ Conversations✓ Customers✓ Attachments✓ Knowledge Base

What we migrate

  • Tickets. Support cases with status, priority, assignee.
  • Conversations. Message threads attached to tickets.
  • Customers. Requester records with custom fields.
  • Attachments. Files and inline images in conversations.
  • Knowledge Base. Help-center articles, categories, sections.
  • Tags. Categorization labels on tickets.
  • Custom Fields. Tenant-defined ticket attributes.

How it runs

  1. Connect

    OAuth or API token authentication; scopes limited to support data.

  2. Map

    We translate ticket statuses, priorities, and channels to the destination's model.

  3. Sample

    Test with 100 tickets across all channels to validate threading and attachments.

  4. Migrate

    Full migration with attachment rehosting and a 301 redirect map between legacy and destination URLs.

What makes helpdesk migrations hard

watch

Ticket ID preservation

Destination IDs are different. We add a custom field with the legacy ID for cross-reference, search, and 301 redirect maps.

watch

Inline image handling

Inline images often link to the old domain. We rehost attachments and rewrite URLs so threads remain intact post-cutover.

watch

Macros, triggers, automations, and SLAs

Macros, triggers, automations, and SLA policies are not migrated as data — they are rebuilt natively in the destination helpdesk, either by us as part of setup or by your team from our inventory.

watch

Agent and group mapping

Agent users are matched by email. Groups, teams, and routing rules are configured in the destination separately.

Questions, answered

Helpdesk migration questions

How long does a helpdesk migration take?

Most helpdesk migrations finish in 3–7 days. Large orgs (1M+ tickets) or post-M&A consolidations typically take 2–3 weeks.

Do attachments and inline images come over?

Yes — every attachment migrates with its original ticket. Inline images are rehosted and URLs rewritten so they don't break after cutover.

Will ticket IDs change?

The destination assigns new IDs, but we add a custom field with the legacy ID for cross-reference and search. We also generate a 301 redirect map between old and new URLs.

What about macros, triggers, and SLAs?

Not as data. Macros, triggers, automations, business rules and SLA policies are rebuilt natively in the destination help desk, by us as part of setup or by your team from our inventory.

Do knowledge base articles migrate?

Yes. KB articles, categories, and sections migrate with content intact. Internal links between articles are rewritten to the destination URLs.

Can we keep both helpdesks running during cutover?

Yes. We support delta migrations that catch tickets created or updated during the cutover window so you can switch without freezing support.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote