Migrate from ArkCase to Microsoft Dynamics 365 Sales

ArkCase Person records map to Dynamics 365 Contact. The primary Organization link resolves via AccountId lookup — if the Person has no primary Organization, the record lands without an AccountId and a default organization flag is set for the admin to resolve post-migration.

ArkCase Organization maps directly to Dynamics 365 Account. Organization hierarchies (parent/child) map to the Parent Account field. Multi-address Organizations map to Account.Addresses with the primary address flagged; secondary addresses migrate as Address object rows if Dynamics 365 multi-address is enabled.

ArkCase Case maps to Dynamics 365 Case (incident entity). Case status values (Active, Pending, Closed, etc.) map via value mapping to the Dynamics Case.Statuscode pick-list. Priority maps to Priority. The ArkCase CaseId is preserved in a custom Source_System_ID__c field for traceability and delta-run de-duplication.

ArkCase Complaint is a specialized Case subtype. We merge Complaints into the Case entity and add a custom Complaint_Type__c field to distinguish them from standard Cases. The complaint reason and filing-party fields map to custom fields on the Case record. If your ArkCase setup uses a separate Complaint entity with its own workflow, a custom Case origin field tracks this.

ArkCase Task maps directly to Dynamics 365 Task. Task status values (Open, In Progress, Completed, etc.) map to Task.Statuscode pick-list values. Task Priority maps to Priority. Assignee resolution uses email matching against Dynamics 365 users. Unmatched assignees are flagged before migration for admin assignment.

ArkCase Communication records of type 'Email' migrate to Dynamics 365 Email (email activity). The email subject, body, from, to, and cc fields map directly. Original timestamps (sent date, received date) are preserved in custom datetime fields. Email direction (inbound/outbound) is stored in a custom Email_Direction__c field.

ArkCase Documents do not migrate as Dynamics native attachments because Dynamics 365 Sales does not have a native ECM layer. Instead, we create SharePointDocumentLocation records pointing to the ArkCase-managed SharePoint repository, and store document metadata (filename, size, version, create date, created-by user) as custom fields on a Note record linked to the parent Case or Contact. Actual binary files remain in the SharePoint repository with URL preserved for re-linkage post-migration.

ArkCase stores contact PII in encrypted fields (encryptedFirstName, encryptedLastName, encryptedEmail, encryptedPhone) for FedRAMP and HIPAA compliance. Dynamics 365 has no native encrypted-field type. These migrate to custom text fields named ArkCase_Encrypted_FirstName__c, ArkCase_Encrypted_LastName__c, etc. After migration, the encrypted values must be decrypted and re-identified by your compliance team and written to the standard Contact fields. We flag records with active encrypted values in a custom ArkCase_PII_Requires_Review__c boolean.

ArkCase maintains a full user-action audit trail across all entity types. Dynamics 365's audit log captures field-level before/after values for changed fields only — it does not record every user action. We create a custom ArkCase_Audit_Log__c table in Dataverse and populate it with the ArkCase audit records, preserving the user, action, entity, record ID, and timestamp. This table is read-only post-migration and is used for compliance retrieval.

ArkCase BPMN 2.0 workflow definitions (FOIA intake, ROI processing, data-privacy workflows) have no equivalent in Dynamics 365 Sales. We export the workflow definitions as JSON blueprints and deliver them alongside a Power Automate rebuild guide that maps each BPMN task to an equivalent cloud flow or desktop flow. The actual automation must be rebuilt manually by your Power Automate admin or FlitStack's automation team as a separate engagement.

ArkCase links Persons to Cases via a many-to-many association table. Dynamics 365 Cases have a primary CustomerId field pointing to an Account or Contact. We map the primary Person on a Case to the CustomerId; additional associated Persons are stored as custom multi-select text (ArkCase_Secondary_Parties__c) or linked via the Contact entity's RegardingObjectId on the Case.

ArkCase allows N:N Person-to-Organization associations. Dynamics 365 Contacts have one primary AccountId and use AccountContactRelation for additional organization links. We migrate the most-recently-linked Organization as the primary AccountId and surface the rest as AccountContactRelation rows. The relationship type field (e.g., Legal Counsel, Respondent) maps to the AccountContactRelation.Roles field.