Front to Intercom migration

Configuration such as automations, macros and views is not data, so it is set up again in Intercom. Anything with no equivalent in Intercom 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 Front, so your team keeps working during the full run, and a delta sync at cut-over moves anything created or changed since.

None documented. Intercom's Syncing and importing content collection has no Front source, and no Front conversation importer is documented in Intercom's help centre. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.

Front Core API: 50 requests a minute on Starter, 100 on Professional and 200 on Enterprise, per company rather than per token, with a burst allowance of half the plan limit; some routes have their own tier limits, such as search at 40 percent of the rate limit. 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.

Several handles per contact have to be de-duplicated into one Intercom contact. Comments sit on a separate endpoint from messages and must be merged into the thread as notes in the right order. Front's per-company API limit is low, so large histories take a long, paced read.

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.