Migrate from Agile CRM to Salesforce Service Cloud

Agile CRM Company records map directly to Salesforce Account. The Company domain_name or website field becomes the Account Website. Company is imported first because every Contact in Salesforce must reference an Account (or be converted from a Lead). We use Company name as the dedupe key and resolve any duplicate Company names by domain match before insert to prevent duplicate Account creation.

Agile CRM Contacts map to Salesforce Contacts with AccountId resolved from the Company mapping. All native fields (FirstName, LastName, Email, Phone, Title) map directly. Custom fields migrate as custom Contact fields (__c) with type preserved (text, number, date, picklist). We set AccountId via a pre-computed lookup map keyed on Company name before Contact insert to satisfy the required relationship.

Agile CRM Deals map to Salesforce Opportunity. The deal's custom_milestone property maps to StageName; custom_deal_track maps to RecordType and Sales Process that we configure in Salesforce before migration. Deal value, expected close date, owner, and linked Contact and Company associations migrate with WhatId resolved to AccountId and WhoId to ContactId. Closed-Lost reason custom fields become LossReason.

Agile CRM Helpdesk Cases map to Salesforce Case with Case Number preserved as an external reference field, Status mapped to Case Status, Priority mapped to Case Priority, and Origin mapped from the Agile case channel field (email, phone, chat). Case conversation threads migrate as EmailMessage records linked to the Case via ParentId. Agent assignments resolve by email match to Salesforce User records in the Case OwnerId field.

Agile CRM Groups function as team-based access partitions and case queues. We migrate Group membership and map it to Salesforce Queues (Group object with Type = Queue) plus Case Assignment Rules. Assignment Rule entries are configured to route cases to the correct Queue based on case Origin, Priority, or a custom field. Group names that conflict with existing Salesforce Profile or Permission Set names are renamed during scoping to avoid permission conflicts.

Agile CRM Labels are used to tag and categorize Contacts, Deals, and Cases. We migrate Labels as Salesforce Tags (Topic object with TopicAssignment records linked to the parent record) for content classification, or as multi-select picklist custom fields if the customer prefers a structured field over a free tagging model. The customer selects the strategy during scoping.

Agile CRM Tasks map to Salesforce Task with Status, Priority, ActivityDate, Subject, and Description preserved. Task assignment resolves by matching Agile owner email to Salesforce User Id in the OwnerId field. Tasks linked to Contacts resolve WhoId; tasks linked to Deals resolve WhatId as the Opportunity Id. Due dates and reminders transfer to Salesforce Task fields.

Agile CRM call activity records map to Salesforce Task with TaskSubtype = Call. Call disposition, duration in seconds, and recording URL migrate to custom Task fields. ActivityDate is preserved from the Agile timestamp to maintain chronological ordering in the Salesforce Activity timeline.

Agile CRM email engagements migrate to Salesforce EmailMessage records (the message content and headers) linked to a parent Task record (the timeline entry). The WhoId on Task points to the Contact; the ParentId on EmailMessage points to the Case if the email is case-related. We use the Bulk API 2.0 for this phase given typical email volume.

Agile CRM meeting engagements map to Salesforce Event with StartDateTime, EndDateTime, Subject, Location, and Description preserved. Attendees migrate as EventRelation records linking the Event to the Contact or Account. Calendar invites and body content transfer as Salesforce Notes attached to the Event record.

Agile CRM Notes (engagement type NOTE) migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, Opportunity, or Case. Note body transfers as rich text with image attachments preserved as ContentDocument records. We resolve the parent record reference at migration time using the pre-built lookup map.

Agile CRM file attachments stored per record (Contact, Company, Deal, or Case) migrate as Salesforce ContentDocument records attached via ContentDocumentLink to the parent record. We export binary attachments via the Agile CRM file export endpoint, upload to Salesforce via the Connect API, and re-associate by matching the parent record's external ID to the Salesforce record ID resolved during migration.

Agile CRM custom fields on Contacts, Companies, Deals, and Cases are exposed with type=CUSTOM in the REST API. We discover all custom fields during the export audit, map them to Salesforce custom fields of equivalent type (Text, Number, Date, Picklist, Checkbox, Formula), pre-create the Salesforce custom fields in a Sandbox org for validation, then deploy to production before the data migration phase begins.

Agile CRM owners (user IDs on Contacts, Companies, Deals, Cases, and Tasks) are resolved by email match against the Salesforce destination User table. Any Agile owner without a matching Salesforce User goes to a reconciliation queue and the customer's admin provisions the missing Users before record import resumes. OwnerId is a required reference on Opportunity and Case, making this step a hard gate before those phases begin.