Migrate your Agile CRM data

Contacts are the primary record in Agile CRM, storing name, email, phone, social links, tags, and lead score. Custom fields are supported and exposed as type=CUSTOM in the REST API. We map Contacts field-by-field, preserving all standard properties and rendering custom field values into the destination's equivalent custom property schema.

Companies (also called Accounts) store business records linked to Contacts. Agile CRM enforces a single link from Contact to Company, so We validate that every Contact has at most one associated Company during the import sequence to avoid orphaned links or silent duplicate creation.

Deals in Agile CRM support Custom Deal Milestones and Custom Deal Tracks. Milestones map to stage names but track logic (multi-lane pipelines) is platform-specific. We preserve deal value, stage, owner, expected close date, and milestone history; custom track logic is translated to the destination pipeline structure where supported.

Helpdesk Cases are Agile CRM's primary service object. They support Groups, Labels, Canned Responses, Views, and custom fields. We migrate Cases with their conversation threads, attachments, and agent assignments intact, mapping Agile's status lifecycle to the destination's ticket state model.

Tasks in Agile CRM are unlimited on all paid tiers and support assignment, due dates, priorities, and linked contact/company/deal associations. We migrate Tasks preserving the linked-entity relationships and owner assignment.

Documents are stored per-record in Agile CRM and can be attached to Contacts, Companies, or Deals. We migrate binary attachments via the file export endpoint, re-associating them to the correct record in the destination using record ID mapping established during the scoping phase.

Custom fields are supported on Contacts, Companies, Deals, and Cases via Admin Settings. Agile CRM exposes them with type=CUSTOM in the REST API. We discover all custom fields during the export audit, map their data types to the destination schema, and flag any unsupported field types (e.g., complex formula fields) for manual review.

Agile CRM's automation rules and workflows are not exposed via the REST API — the platform stores workflow logic internally and does not provide a machine-readable export of trigger conditions, action sequences, or wait-step configurations. We do not migrate workflows. We rebuild revenue-critical automations as destination-native workflows post-migration, starting with deal-stage-change triggers and follow-up sequences.

Marketing Campaigns in Agile CRM include email sequences, web engagement popups, and landing pages. Campaign records (metadata, step counts, node limits) are accessible, but the full email content and step logic require separate extraction. We migrate campaign metadata and contact association lists; content and automation step details are exported separately for manual rebuild in the destination.

Groups in Agile CRM function as team-based access partitions and helpdesk queues. We migrate Group membership and map it to the destination's team or queue structure, flagging any naming conflicts.

Labels are used to tag and categorize Contacts, Deals, and Cases. We migrate Labels as tags, preserving the per-object associations for each record.

Activities in Agile CRM log calls, emails, meetings, and notes tied to Contacts or Deals. We migrate the full activity timeline including timestamp, owner, type, and notes content, maintaining chronological order in the destination.

Agile CRM exposes 50+ plugins on higher tiers (Google Sync, Shopify, Stripe, Chrome Extension, and others). Plugin configurations are stored per-account but not exposed via API in a transferable format. We flag enabled integrations during scoping and document their connection parameters so they can be reconfigured in the destination platform.