Drift 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 Drift, 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 Drift source and Intercom documents no Drift conversation importer, so history goes in through the Intercom API. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.

Drift API: calls are limited per time window and a rate_limit error (HTTP 429) is returned once they are used up; Drift's developer docs publish no fixed number, so the read is paced on those responses. Conversations are listed up to 100 a page and messages come 50 a page. 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.

Clari + Salesloft announced the gradual sunset of Drift in March 2026 without a published end date, so history is exported early, while API access still works. Drift has no bulk export and no endpoint that lists every contact, so conversations are listed first and contacts are read through each conversation's contactId. Private notes must be written as Intercom notes and bot buttons flattened to text, which is checked on a sample before the full run. Booked meetings are only returned for the last 30 days, so they are exported before anything else.

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.