Migration routes
Pick a route. See exactly what migrates.
Open a route for the objects we move, the known risks and the timeline, or start from the platform you are on today.
All routes
Moving from
Moving to
- Zendesk to FreshdeskWe move your Zendesk history into Freshdesk: tickets with every public reply and internal note, attachments, users, organizations, custom fields and Help Center articles. Zendesk's own export leaves comments out of CSV and stops at 200,000 tickets in XML, so we read everything through the API and pace the load to your Freshdesk plan's limits. Your team keeps working in Zendesk until cutover.7 object typesSee what migrates
- Freshdesk to ZendeskWe move your Freshdesk history into Zendesk: tickets with every reply and note, attachments, contacts, companies, custom fields and knowledge base articles. Freshdesk's ticket list only returns the last 30 days by default, so we page through your full history by date, then load it through Zendesk's Ticket Import API, which keeps the original created, updated and solved dates. Your team keeps working in Freshdesk until cutover.7 object typesSee what migrates
- Zendesk to Salesforce Service CloudA Zendesk to Salesforce Service Cloud migration turns tickets into Cases, end users into Contacts and organizations into Accounts. The hard part is history: each public reply becomes an EmailMessage and each internal note an internal feed item, with original dates and authors. Zendesk stays live until the final delta sync, which copies anything changed during the run.14 object typesSee what migrates
- Salesforce Service Cloud to ZendeskMoving from Salesforce Service Cloud to Zendesk means turning each Case, and the emails, case comments and Chatter posts around it, into one Zendesk ticket thread. We import tickets with their original created and solved dates, carry files Case by Case, and move Knowledge into the Help Center. Salesforce keeps running until cutover, and a final delta sync copies anything changed during the run.14 object typesSee what migrates
- ServiceNow to FreshserviceWe move incidents, problems, changes, request items, requesters, departments and the knowledge base from ServiceNow into Freshservice, with work notes and comments kept as separate private and public notes. An engineer maps states, priorities and groups with you, runs the import in dependency order, and reconciles counts on both sides before you cut over.10 object typesSee what migrates
- Freshservice to ServiceNowWe move tickets, problems, changes, service requests, requesters, departments and solution articles from Freshservice into ServiceNow, with private notes and public replies kept as work notes and comments. An engineer loads everything through staging tables and transform maps with notifications off, keeps the original dates, and reconciles counts on both sides before you cut over.10 object typesSee what migrates
- HaloITSM to FreshserviceWe move tickets, problems, changes, users, clients, agents and your knowledge base from HaloITSM into Freshservice, with each ticket's actions kept as ordered public and private notes. An engineer maps ticket types, statuses, clients and custom fields with you, imports in dependency order, and reconciles counts on both sides before you cut over.9 object typesSee what migrates
- Freshdesk to FreshserviceWe move IT tickets, conversations, contacts, companies, agents and the knowledge base from Freshdesk into Freshservice, splitting tickets into incidents and service requests during the move. An engineer agrees the type, department and field mapping with you, imports in dependency order, and reconciles counts on both sides before you cut over. Customer support can stay on Freshdesk.7 object typesSee what migrates
- ServiceNow to Jira Service ManagementWe move incidents, requests, problems, changes, users, the knowledge base and CMDB items from ServiceNow into Jira Service Management, Confluence and Assets. Work notes stay internal and customer comments stay visible. Our ITSM team runs this route as an engineer-led migration, maps states and request types with you, and reconciles counts on both sides before cutover.13 object typesSee what migrates
- Zendesk to Jira Service ManagementThis is a one-time data migration, not an integration: we move tickets, public replies, internal notes, attachments, end users, organizations and Help Center articles out of Zendesk and into Jira Service Management and Confluence. Internal notes stay internal and customers keep their organizations. Our ITSM team runs this route as an engineer-led migration, maps forms and statuses with you, and reconciles counts on both sides before cutover.13 object typesSee what migrates
- Cherwell to ServiceNowCherwell Service Management reaches end of life on 31 December 2026, and Ivanti gives 30 December 2026 as the last day of normal licensed access. We move incidents, requests, problems, changes, journals, attachments, CIs and knowledge into ServiceNow, with internal notes and customer updates kept apart and original dates preserved. Our ITSM team runs this route as an engineer-led migration, planned backwards from your cutover date.14 object typesSee what migrates
- BMC Helix ITSM to ServiceNowWe move incidents, problems, changes, work orders, people, support groups, knowledge and CMDB data from BMC Helix ITSM (formerly Remedy) into ServiceNow, with Internal and Public work info kept apart. Our ITSM team runs this route as an engineer-led migration: Foundation data first, test loads in sub-production, and a reconciled cutover.14 object typesSee what migrates
- Cherwell to Jira Service ManagementA Cherwell to Jira Service Management migration turns incidents and service requests into work items, Note journals into internal comments and Customer Request journals into public comments. Ivanti lists Cherwell Service Management with an end-of-life date of 31 December 2026, and 30 December is the last day of normal licensed access. Cherwell stays live until the final delta sync.15 object typesSee what migrates
- Freshdesk to GorgiasGorgias has no built-in Freshdesk importer, so a Freshdesk to Gorgias migration is an API load from start to finish. The catch is on the Freshdesk side: a plain ticket list shows 30 days and ends at 30,000 tickets. We read your whole history in date windows, and Freshdesk stays live until the delta sync.10 object typesSee what migrates
- Freshdesk to HubSpotLeaving Freshdesk for HubSpot starts with finding the whole history: Freshdesk's ticket list looks back 30 days by default, so we read every year in date windows. Tickets then land in a Service Hub pipeline beside your CRM contacts and companies, with replies as email activities, private notes as notes and public notes clearly marked. Agents keep using Freshdesk until the catch-up sync.16 object typesSee what migrates
- Freshdesk to IntercomA Freshdesk to Intercom migration turns tickets into Intercom conversations or tickets, contacts into users or leads, and agents into admins. The hard part is the history: Freshdesk's ticket list returns only 30 days by default. Freshdesk stays live until the final delta sync.11 object typesSee what migrates
- Freshservice to HaloITSMA Freshservice to HaloITSM migration turns tickets, problems, changes and service requests into Halo tickets, and each reply or private note into an action. Halo documents no Freshservice importer, so the move runs on both APIs, paced by Halo's limit of 700 requests in any five minutes. Freshservice stays live until the final delta sync.14 object typesSee what migrates
- Freshservice to Jira Service ManagementA Freshservice to Jira Service Management migration turns incidents and service requests into work items with the right request type, replies into public comments and private notes into internal comments. The hard part is the read side: Freshservice lists a month of tickets and ten conversations by default. Freshservice stays live until the final delta sync.13 object typesSee what migrates
- HubSpot to Salesforce Sales CloudA HubSpot to Salesforce Sales Cloud migration sends companies to Accounts, deals to Opportunities and each contact to either a Lead or a Contact, chosen by lifecycle stage. The work sits on both ends: HubSpot's exports leave activities out, and Salesforce accepts original dates, Task subtypes and won or lost status only at insert. HubSpot stays in use until the final delta sync.15 object typesSee what migrates
- Intercom to FreshdeskAn Intercom to Freshdesk migration turns conversations into tickets, admins into agents and teams into groups. The hard part is the pace, set by Freshdesk's per-minute cap on ticket creation. Intercom stays live until the final delta sync.11 object typesSee what migrates
- Intercom to ZendeskAn Intercom to Zendesk migration turns conversations into tickets, contacts into end users and companies into organizations. The hard part is the read, because Intercom has no bulk export of message text. Intercom stays live until the final delta sync.14 object typesSee what migrates
- Jira Service Management to FreshserviceA Jira Service Management to Freshservice migration turns work items into tickets, public comments into replies and internal comments into private notes. Freshservice sets the limits on the way in: 40 MB of files per ticket, incidents through the Tickets API and requests through the service catalog. Jira stays live until the final delta sync.14 object typesSee what migrates
- Jira Service Management to ServiceNowA Jira Service Management to ServiceNow migration splits Jira work items into incidents, problems, changes and requested items, and turns each comment into additional comments or work notes. Records load through import sets with business rules off, so no old change starts an approval. Jira keeps running until cutover, and a delta pass updates what changed.13 object typesSee what migrates
- Jira Service Management to ZendeskMoving from Jira Service Management to Zendesk turns each work item and its comments into one Zendesk ticket, imported with its original created, updated and solved dates. Internal comments arrive as internal notes, customers as end users and Confluence knowledge pages as Help Center articles. Jira keeps running until cutover, and a delta pass re-imports what changed.13 object typesSee what migrates
- Pipedrive to HubSpotA Pipedrive to HubSpot migration moves your sales pipeline into Smart CRM: persons become contacts, organizations companies, and deals keep their pipeline, stage and value. Activities and notes land on the right timelines at their original time, and Pipedrive keeps running until a final delta sync.8 object typesSee what migrates
- Salesforce Sales Cloud to Dynamics 365 SalesA Salesforce to Dynamics 365 Sales migration moves Accounts, Contacts, Leads and Opportunities into Dataverse tables, and turns each Task, Event and email into an activity whose people are activity parties. The hard parts are closed deals, which Dynamics closes through its own messages, files above the attachment limit, and ownership by business unit. Salesforce stays live until the final delta sync.12 object typesSee what migrates
- Salesforce Sales Cloud to HubSpotA Salesforce Sales Cloud to HubSpot migration turns Accounts into companies, Opportunities into deals and open Leads into contacts with a lifecycle stage. What needs care is HubSpot's side: only deals keep an original Create date, imported activities cannot be corrected by a second import, and line items belong to one deal. Salesforce stays live until the final delta sync.13 object typesSee what migrates
- Zendesk to FreshserviceA Zendesk to Freshservice migration moves a support desk onto an ITSM platform, so every Zendesk ticket lands as an incident or a service request. Public comments become replies and internal notes private notes, in thread order. End users become requesters and organizations departments. Zendesk stays live until the final delta sync copies what changed during the run.13 object typesSee what migrates
- Zendesk to GorgiasA Zendesk to Gorgias migration has to go further than Gorgias's own Zendesk importer, which skips attachments and ratings, closes pending and solved tickets and stops at two years. We move the full Zendesk history through the API, and Zendesk stays your live inbox until the final delta sync.11 object typesSee what migrates
- Zendesk to HubSpotA Zendesk to HubSpot migration moves support history onto the CRM your sales team already uses: tickets into a Service Hub pipeline, end users into contacts and organizations into companies. Every public reply arrives as an email activity and every internal note as a note, at its original time. Zendesk keeps running until a final delta sync.16 object typesSee what migrates
- Zendesk to IntercomA Zendesk to Intercom migration turns each ticket into an Intercom conversation or an Intercom ticket, end users into contacts and organizations into companies. The hard part is the landing: Intercom starts a conversation only from a contact, so tickets opened by agents need a convention. Zendesk stays live until the final delta sync.12 object typesSee what migrates
- Zoho CRM to HubSpotA Zoho CRM to HubSpot migration moves your customer records into Smart CRM: contacts and accounts become contacts and companies, and deals keep their pipeline and stage. Notes, emails and files are read apart from the records and rejoined to them, and Zoho keeps running until a final delta sync.10 object typesSee what migrates
Platforms
Start from your current platform
Open the platform you are moving off to see the routes we run from it and what each one carries across.
- ZendeskSee routes from here
- FreshdeskSee routes from here
- ServiceNowSee routes from here
- FreshserviceSee routes from here
- ManageEngineSee routes from here
- Jira Service ManagementSee routes from here
- HaloITSMSee routes from here
- CherwellSee routes from here
- BMC Helix ITSMSee routes from here
- Salesforce Service CloudSee routes from here
- Dynamics 365 SalesSee routes from here
- GorgiasSee routes from here
- HubSpotSee routes from here
- IntercomSee routes from here
- PipedriveSee routes from here
- Salesforce Sales CloudSee routes from here
- Zoho CRMSee routes from here
Don't see your route?
We add connectors on demand. Tell us the two platforms you are moving between and we will scope the route with you. See every connector
Scope my migration
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.