Agent skill · software engineering · jeremylongshore
intercom-migration-deep-dive
Use when migrating from Zendesk/Freshdesk/HelpScout to Intercom, bulk-importing contacts, or re-platforming to Intercom with the contacts, conversations, and articles APIs. Trigger with phrases like "migrate to intercom", "intercom migration", "import contacts to intercom", "switch to intercom", "zendesk to intercom", "intercom data import".
Why this skill is useful
Adds executable TypeScript scripts for migrating data to Intercom that aren't in public documentation.
What it needs
Requires npm installed locally. Requires intercom account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Intercom Migration Deep Dive Overview Comprehensive guide for migrating to Intercom from other platforms (Zendesk, Freshdesk, HelpScout) or bulk-importing data. Covers contact import, company import, tags, Help Center articles, orchestration, and post-migration validation. The full runnable TypeScript for every phase lives in references/implementation.md; this file carries the workflow and the first-phase skeleton so you can follow it end to end, then drill into the reference for depth. Prerequisites Intercom workspace with an access token exported as INTERCOMACCESSTOKEN Source system data exported (CSV or API access) The intercom-client SDK installed (npm install intercom-client) Feature flag infrastructure for gradual cutover Rollback strategy tested Authentication All scripts read the workspace access token from the environment — never hard-code it. Create the token in the Intercom Developer Hub (Settings → Developers → your app → Authentication), then: Migration Types Type Complexity Duration Risk ------ ----------- ---------- ------ Contact import Low Hours Low Zendesk/Freshdesk migration Medium 1-2 weeks Medium Full re-platform (with history) High 2-4 weeks High Help Center migration Medium Days Low Instructions Run the phases in dependency order. Each phase is a standalone function in references/implementation.md; the orchestrator in Step 5 chains them. 1. Contacts (Step 1) — idempotent: search by externalid/email, then update or create. Stamp migratedfrom + migrationdate custom attributes so rollback can find migrated records. Skeleton below. 2. Companies (Step 2) — import before attaching contacts; contacts reference companies. 3. Tags (Step 3) — create each tag, apply to its contacts, skip missing (404) contacts instead of aborting. 4. Articles (Step 4) — group into Help Center collections by category, creating each collection once. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/intercom-migration-deep-dive