Skip to content
Get a quote

What is a delta migration in help desk migration?

Short answer

A delta migration is a second, smaller pass after the main migration. It moves only the tickets, comments and contacts created or updated since the full run started. Agents keep working in the old help desk, and the delta catches up at cutover, with no long freeze. It needs a reliable "changed since" signal from the source.

By

How it works

A help desk never stops. While a full migration of 500,000 tickets runs, customers keep writing in and agents keep replying. A delta migration handles this in three steps:

  1. Full run. Move everything as it was at time T0, while agents keep working in the old help desk.
  2. Delta. At cutover, move only the records created or updated after T0, such as new tickets and new comments on old tickets.
  3. Switch. Point email forwarding, widgets and channels at the new help desk.
Without a deltaWith a delta
Agent downtimeFreeze for the length of the full runMinutes to hours at cutover
Tickets changed during the runLost or re-entered by handCaptured
RiskPressure to rush the full runThe full run can take as long as it needs

What the native tools do / where they stop

No major help desk offers “delta migration” as a feature. The pieces exist as APIs. Zendesk’s Incremental Export API returns “items that changed or were created … since the last request”, and Zendesk recommends cursor-based exports, with an end_of_stream flag to show you’ve caught up. File exports don’t work for this: Freshdesk’s ticket export “will NOT give you the entire conversation” or archived tickets, so a CSV can’t carry a delta of new comments.

The other detail the docs don’t cover is what a delta does to a ticket that changed in both systems. Most delta tools overwrite the destination with the newer source version. So the rule at cutover is simple: agents work in one system at a time.

Checklist for a clean delta

  1. Record T0 precisely, in UTC, when the full run starts.
  2. Make sure every record keeps its source ID, so the delta updates instead of duplicating.
  3. Include new comments on old tickets, not just new tickets.
  4. Run a rehearsal delta a day before cutover to time it.
  5. Switch channels only after the final delta finishes.

Where FlitStack AI fits

Delta migration is part of every FlitStack AI migration. It catches tickets created or updated during the cutover window, so support doesn’t freeze. See help desk migrations.

Questions, answered

A few useful answers.

How is a delta different from a sync?

A delta is a one-off catch-up at cutover. A sync keeps two systems aligned continuously in both directions. Most help desk moves need a delta, not a sync.

What if agents already edited a ticket in the new help desk?

A delta that overwrites will replace those edits with the source version. Either keep agents out of migrated tickets until cutover, or review conflicts before the delta runs.

Do native tools offer delta migrations?

Not as a feature. Zendesk's Incremental Export API gives you the 'changed since' data on the Zendesk side, but you build the delta yourself.

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