“A helpdesk migration is complete when the next reply has the old context, the new owner, and a tested channel path.”
Migration plan
Move support history into Ochre without losing the customer story
Plan the import from Zendesk, Intercom, or Help Scout, map the data your team depends on, preserve searchable history, cut channels over deliberately, and launch with QA and rollback controls already assigned.
Import plan
3 sources
Zendesk, Intercom, and Help Scout migrations start with export scope, API access, and record ownership.
History
Preserved
Conversation transcripts, internal notes, attachments, tags, timestamps, and authors remain usable after cutover.
Cutover checklist
Migration control room
Cutover checklist
Migration control room
HANDL.
3
RESOL.
14
AVG C.
99%
SPEND
$0.19
Maria Chen
nowCan we change seats before renewal?
Maria Chen / #TKT-c_58babc0a02
Subject Can we change seats before renewal? · Channel Email
Can we change seats before renewal? We need to add two teammates this week.
You are on Starter with 3 included seats. I can switch you to Per Seat and keep your May 28 renewal date unchanged.
Operating model
Scroll through the actual operating path.
Each card locks into place as you move down the page, updating the product scene above and keeping the current workflow step in focus.
Proof points
Built from the work support actually does.
“History has to survive as searchable support memory, with enough source metadata to reconcile anything that looks wrong.”
Start with one clear support path, then add the depth your team needs.
Ochre keeps the workflow concrete: one inbox, one customer story, one visible AI review path, and a practical route into the rest of the platform.