Migrate your Intercom data

Contacts (Users and Leads) are first-class API objects with a stable schema including email, name, custom attributes, and owner assignment. We migrate contacts 1:1 and preserve all standard and custom properties during import and export.

Companies are linked to Contacts and expose a standard set of attributes (name, plan, monthly_spend, custom attributes). We preserve the company-contact association during migration to maintain context in conversation history.

Conversations are the core Intercom object, containing nested Parts (messages, notes, assignments). We map conversation threads and part types, but note that S3 JSON exports exclude transcripts — we use the REST API to retrieve full conversation content where available.

Messages are nested inside Conversation Parts and include body text, attachments, and delivery metadata. We sequence messages in chronological order and flag any that are redacted or inaccessible via API as part of the migration audit.

Admins are agent accounts with roles, Avatars, and away/available states. We migrate admin identity mapping so conversation assignments, activity logs, and ownership reflect the correct agents in the destination platform.

Teams group Admins for routing and inbox assignment. We preserve team membership and routing rules during migration to maintain the same escalation paths in the target system.

Tags are labels applied to Contacts and Conversations for segmentation. We migrate all tags and reapply them to the corresponding objects in the destination workspace.

Segments are dynamic audience definitions based on Contact attributes and behavior. We map the membership snapshot at migration time, as dynamic recomputation of segment membership is destination-platform-dependent.

Help center Articles have titles, bodies, authors, collections, and publication states. We migrate Article content and metadata, but public visibility settings and article-specific URLs may need manual verification after cutover.

Tickets are a structured support object introduced more recently in Intercom's model, distinct from the Conversation-first workflow. We map ticket fields, statuses, and custom ticket attributes, noting that not all destination platforms have a parallel Ticket object.

Custom Attributes extend Contacts, Companies, and Conversations with workspace-specific fields. We identify all custom attribute definitions and their types during scoping, then apply field-level mapping to the destination's equivalent custom field mechanism.

Custom Objects are user-defined data structures with their own schema and relationships. We migrate Custom Object Instances via the REST API using the custom_object_instances endpoints, mapping to the destination's equivalent custom object type.

Data Attributes expose the full workspace schema including both standard and custom fields across all object types. We audit the attribute list via the API to generate the complete field inventory before mapping to the destination schema.

Activity Logs record admin actions (assignment changes, status updates, notes added). We migrate the log entries where API access is available, noting that log retention may be limited and that high-volume log exports require pagination handling.