Migrate from AgileCase to Microsoft Dynamics 365 Sales

AgileCase stores contacts inside cases. FlitStack extracts all unique contacts, deduplicates by email address, and loads them as Dynamics 365 Contact records. A primary CaseId reference is preserved as a custom field on the contact for traceability. FlitStack also merges duplicate contacts identified by phone number, and flags email-less contacts for Lead routing.

AgileCase contacts without an email address cannot map to Dynamics 365 Contact (which requires Email as a required-like field for duplicate detection). These records route to the Dynamics Lead entity instead, with a flag noting their original AgileCase source. The Lead retains the contact's name, phone, and address fields, and the source flag enables reporting on the origin of these records.

AgileCase companies extract to Dynamics 365 Account records. The primary contact link from the case becomes Account's primary contact lookup. Parent-child company hierarchies in AgileCase map to Account.ParentId in Dynamics. FlitStack also validates that each parent company exists before linking, and any orphaned child companies are queued for manual resolution. The account record retains the original AgileCase company ID in Source_ID__c for reconciliation.

AgileCase Case objects map to Dynamics 365 Opportunity records — each case becomes one opportunity. Case name becomes Opportunity.Name; case amount maps to Opportunity.Amount; case closed date maps to Opportunity.CloseDate. FlitStack also copies the case description into the Opportunity Description field and maps any custom case fields to corresponding Dataverse columns on the Opportunity. If the case includes a reference to a primary contact, FlitStack resolves the ContactId lookup before loading the opportunity.

AgileCase case-status pick-list values (e.g., Open, In Progress, Resolved, Escalated) map to Dynamics Opportunity Stage values per pipeline. We create a Dataverse option-set for case status and map each value explicitly — no default mapping is assumed. If a case status value does not match an existing stage in the target pipeline, FlitStack creates a new stage entry in the Dataverse option-set and flags it for review, ensuring no status is lost during migration.

AgileCase priority levels (Low, Medium, High, Critical) have no native Dynamics equivalent on Opportunity. We create a custom option-set field Priority__c on the Opportunity entity and map values one-by-one. The custom field is added to the Opportunity form layout and included in Power BI reports for filtering by priority. During migration, any unmapped priority values are logged and resolved by your Dynamics admin before go-live.

AgileCase case owner resolves by email match against Dynamics 365 system users. Unmatched owners are flagged with a custom field AgileCase_Original_Owner__c for manual assignment before go-live. The matching logic also checks for duplicate email addresses and selects the most recently active user account. If no match is found, the opportunity is placed in a dedicated queue for your admin to assign an owner manually, ensuring no records are left without an owner after cutover.

Every AgileCase custom field maps to a Dataverse column of the equivalent data type — text, number, date, pick-list, boolean. Dynamics 365 Sales Professional enforces a per-entity column limit; we validate field count against the license tier before migration. If the custom field count exceeds the allowed limit, FlitStack flags the excess fields and recommends either consolidating fields into a JSON blob or upgrading to Sales Enterprise before proceeding.

AgileCase file attachments on cases download to local storage, then re-upload to Dynamics 365 SharePoint document locations or Dataverse file columns, linked back to the Opportunity record by the original case ID. FlitStack also validates file size against the 115 MB Dataverse limit and splits any oversized attachments into smaller chunks before uploading. File metadata such as original creation date and author are preserved in the SharePoint column properties.

AgileCase activity logs (calls, emails, meetings) attached to a case map to Dynamics 365 Task and Email records with the Opportunity as the regarding object. Original activity type, timestamp, and notes are preserved. FlitStack also maps the original contact associated with the activity to the RegardingObjectId field, ensuring that the related contact is linked in Dynamics. If an activity type has no direct equivalent, it is stored as a generic Task with a custom type field.

AgileCase workflow rules and case-plan scripts cannot import into Dynamics 365. FlitStack exports the workflow definitions as a structured JSON package so your Dynamics admin can reference them when rebuilding in Power Automate. The JSON includes trigger conditions, action steps, field update logic, and any custom script snippets. FlitStack also provides a mapping guide that links each AgileCase case-plan step to equivalent Power Automate connectors, helping you replicate the automation flow efficiently.

AgileCase stores up to 180 days of audit history on Professional plans and 3 years on Business plans. Original create and update timestamps migrate as custom datetime fields on each Dynamics record — CreatedDate in Dynamics is set at migration time.