Migrate from Agile CRM to Intercom

Agile CRM Contacts map directly to Intercom Contacts via the Contacts API. We preserve name, email, phone, social links, tags (from Agile Labels), and lead score as a custom attribute. Agile custom fields on Contact migrate as Intercom custom attributes. The primary email address is used as the deduplication key. Contacts are imported first so that subsequent record types (Companies, Conversations) can reference them.

Agile CRM Companies (Accounts) do not have a direct Intercom equivalent because Intercom's model is contact-centric. We have two migration strategies. In the first, we store the Company name, domain, and address as custom attributes on each linked Contact. In the second, we create Intercom Companies via the Companies API (available on specific Intercom plans) and link Contacts to them. The choice depends on the customer's Intercom plan tier and whether they need per-company reporting in Intercom.

Intercom has no Deal or Opportunity object, so active pipeline stages, deal milestones, and track assignments do not migrate. We preserve closed-won Deal values (total revenue) as a custom attribute on the associated Contact for reporting continuity. We flag this limitation during scoping and recommend the customer evaluate Intercom's native Revenue workspace or a third-party pipeline integration if deal tracking is mission-critical.

Active Agile CRM Deal pipeline stages (Appointment Scheduled, Proposal Sent, Negotiation, etc.) have no Intercom equivalent. We do not migrate pipeline stages as records. We deliver a written map of every active Deal stage and its corresponding count so the customer's admin can configure Intercom as a reporting layer if needed. This is a pair-specific limitation that applies to any migration from a pipeline-based CRM to Intercom.

Agile CRM Helpdesk Cases map to Intercom Conversations. Each Case's message thread (including internal notes, agent replies, and customer messages) migrates as Conversation Parts. We preserve the Case number as a custom attribute for cross-reference. Case status (Open, Pending, Resolved, Closed) maps to Intercom's Conversation State. Assigned agent from Agile maps to the Intercom Team or Admin assignment on the Conversation.

Agile CRM Tasks migrate as Conversation Parts with a note type annotation. Due date, priority, and assignment migrate as custom attributes on the part or as tags on the parent Contact. Task-linked-entity relationships (tasks tied to a Contact or Deal) are preserved by attaching the task part to the corresponding Intercom Contact. Tasks without a Contact association are attached to the Contact that owns the conversation thread.

Agile CRM Labels, used to tag Contacts, Deals, and Cases, migrate to Intercom Tags. We preserve the per-object association: a Contact labeled 'enterprise' in Agile carries the 'enterprise' tag in Intercom. Tags are used for segmentation and workflow routing in Intercom. Labels on Deals and Cases are stored as Contact tags for continuity, since Intercom does not have a deal-level tagging model.

Agile CRM Groups (helpdesk queues and team access partitions) map to Intercom Teams. We migrate Group membership by resolving the Agile Group name to the corresponding Intercom Team. If the customer's Intercom plan supports Admin roles, we map Group admins to Intercom Admins. Naming conflicts are flagged during scoping for manual resolution.

Agile CRM Activity records (calls, emails, meetings, notes) attached to a Contact or Deal migrate as Intercom Conversation Parts. Call duration and disposition migrate as custom attributes. Email subject and body migrate as message parts. Meeting details (date, location, attendees) migrate as a note part. We preserve chronological ordering by setting the Conversation Part timestamp to the original Agile Activity timestamp. Activities without a parent Contact are attached to the nearest linked Contact found during the pre-migration relationship audit.

Agile CRM custom fields on Contacts, Companies, and Cases migrate to Intercom custom attributes of equivalent data type (text, number, date, boolean, dropdown). We audit all custom fields during the pre-migration export, map data types, and create the corresponding attributes in Intercom before any records are imported. Custom fields on Deals are not migratable (see Deal limitation above). Validation rules in Agile CRM have no Intercom equivalent and are documented for manual review.

Agile CRM workflow automations (deal milestone triggers, helpdesk routing, lead scoring, drip campaigns) are not exposed via REST API and cannot be exported in machine-readable form. We do not migrate workflows. We deliver a written inventory of every active Agile CRM workflow with its trigger, conditions, actions, and a recommended Intercom Workflow or Rule equivalent. The customer's admin rebuilds them as Intercom Rules and Workflows post-migration. Estimated rebuild time is one to two hours per complex workflow.