Migrate from AgileCase to Salesforce Sales Cloud

AgileCase Cases migrate directly to Salesforce Cases. All standard fields — Subject, Description, Status, Priority, Origin, IsClosed — map 1:1. Custom AgileCase fields require __c custom fields pre-created in Salesforce before migration inserts run. If AgileCase uses custom Status or Priority pick-list values, those need explicit value-by-value mapping to Salesforce pick-list options to avoid insert failures.

AgileCase Contacts migrate to Salesforce Contacts. All standard fields — FirstName, LastName, Email, Phone, MobilePhone, Title, MailingStreet — carry over directly. A Salesforce Contact requires an AccountId lookup to an Account record, so we resolve each contact's primary AgileCase company to a Salesforce Account before inserting contacts. Contacts without a company link attach to a default placeholder Account.

AgileCase Companies map to Salesforce Accounts. The Name, Website, Phone, and Industry fields map directly. Address fields migrate to the Account's billing or shipping address compound field. Parent-company hierarchies in AgileCase map to Account.ParentId in Salesforce. If AgileCase stores annual revenue or employee count, those map to Account.AnnualRevenue and Account.NumberOfEmployees.

AgileCase allows multiple contacts linked to a single Case. Salesforce handles this via the CaseContactRelation object (available as a standard object in most Salesforce editions). Each AgileCase contact-case link becomes a CaseContactRelation record with CaseId and ContactId. The mapping requires the Case and Contact records to already exist in Salesforce, so we sequence this as the final step in the migration.

AgileCase stores the case owner as a user reference. We resolve each owner by email match against Salesforce Users — this is the standard cross-platform owner-resolution pattern. If no matching Salesforce User exists, we flag the record before migration and assign it to a fallback owner that your team specifies. Unresolved owners block Case inserts in Salesforce because OwnerId cannot be null on a Case record.

Every AgileCase custom field requires a pre-created Salesforce custom field before migration. We deliver a custom field manifest that lists each AgileCase field label, its Salesforce API name (with __c suffix), data type, and pick-list values. Your Salesforce admin creates these fields before the migration run. The manifest includes field-level ordering so custom fields are created before the objects that reference them.

AgileCase Enterprise customers who created custom objects map these 1:1 to Salesforce custom objects. Each custom object's fields become Salesforce custom fields on the new custom object. Custom-object records migrate with their parent records using the same dependency-ordered insertion sequence.

AgileCase file attachments re-upload to Salesforce as Salesforce Files — stored as ContentVersion records and linked to the parent Case via ContentDocumentLink. The original file name, MIME type, body content, and any inline text are preserved. File size limits per Salesforce edition apply (25 MB default per file; chunking for larger files).

AgileCase tracks a 180-day audit trail of case field changes on the Professional plan. We extract case history records (field name, old value, new value, changed-by user, changed-at timestamp) and surface them in Salesforce as custom datetime fields on the Case record for cross-object audit continuity. Salesforce's native Case History feature also tracks Status and Priority changes.

AgileCase workflows and automations use AgileCase's proprietary rule engine and do not have a Salesforce equivalent. Triggers, conditions, and actions are not portable between the two platforms. We export your AgileCase workflow definitions as a structured reference document so your Salesforce admin can rebuild equivalent logic in Flow or Process Builder after migration.

AgileCase email templates use a template format that is not directly compatible with Salesforce's HTML-based email template engine. Email templates must be rebuilt manually in Salesforce's Email Template object after migration. We provide a list of all AgileCase email templates with their field merges so your admin can reconstruct them.

AgileCase custom reports (10 on Professional, unlimited on Business and Enterprise) cannot be exported in a format that Salesforce imports. The underlying data migrates, so reports can be rebuilt in Salesforce's reporting module after go-live. We include a report inventory as part of the migration package so nothing is missed during the rebuild phase.