Freshdesk to HubSpot migration

Configuration such as automations, macros and views is not data, so it is set up again in HubSpot. Anything with no equivalent in HubSpot is listed in the written mapping, and you choose what happens to it before anything moves.

Yes. Run it self-serve on the DataGrine platform, or let our migration team handle it end to end. Either way you get 24/7 premium support until the migration is signed off.

No. We only read from Freshdesk, so your team keeps working during the full run, and a delta sync at cut-over moves anything created or changed since.

Partly. HubSpot imports Freshdesk knowledge base articles by Smart copy (Service Hub Professional or Enterprise, up to 400 articles per import, primary language only) and imports records and activities such as notes and emails from files, with associations between them. HubSpot's knowledge base documents no importer that reads Freshdesk tickets directly, so the ticket history is prepared from the Freshdesk API first. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.

Freshdesk: 100 calls a minute on Growth, 400 on Pro and 700 on Enterprise, 50 on trial accounts, shared by every integration on the account; ticket list calls are capped at 40, 100 and 200 a minute respectively. Runs are paced to stay inside that limit, which is why large accounts move in a full run first and a delta at cut-over.

Every ticket needs a pipeline and status decided before it moves, because HubSpot references both by internal ID. Dependent dropdowns need a decision between separate properties and a flattened list before the mapping is signed off. Freshdesk's shared API allowance and HubSpot's daily limit both pace the run, so large histories are moved over several days.

It depends on how many records move and whether you run the migration yourself or have the DataGrine team run it. You get a quote once the records in scope are counted, before anything moves.