Migrate from ArkCase to Salesforce Sales Cloud

ArkCase Persons (individuals involved in cases) map to Salesforce Contacts. The primary organization from ArkCase Person-Organization associations populates Contact.AccountId. Email, phone, and address fields map directly. We preserve ArkCase person type (Complainant, Respondent, Witness) as a custom pick-list field on Contact.

ArkCase Persons flagged as prospective leads (no active case relationship) route to Salesforce Lead. This split is based on an ArkCase person attribute or association flag. Lead conversion in Salesforce creates the Contact and Account later, preserving the original ArkCase Person ID.

ArkCase Organizations map to Salesforce Accounts with direct field mapping for name, address, industry, and employee count. Parent-child organization hierarchies in ArkCase translate to Account.ParentId relationships in Salesforce. The ArkCase organization type classification—Government Agency, Private Entity, or Non-Profit—migrates as a custom pick-list field on Account to preserve the original categorization for reporting and segmentation purposes.

ArkCase Cases map to Salesforce Cases with direct field mapping for case number, subject, description, status, priority, and origin. ArkCase Case Type values map to a custom Case_Type__c pick-list. The case create date and last-modified date are preserved as custom datetime fields since Salesforce CreatedDate reflects migration time, not original creation time.

ArkCase parent-child case hierarchies (parent case, linked cases) map via Salesforce Case.ParentId for direct single-level hierarchy representation. When ArkCase contains multi-level case trees or cross-reference links between unrelated cases, we create a Case_Link__c custom junction object to preserve the full relationship graph accurately with Parent Case ID, Linked Case ID, and Link Type fields.

ArkCase Tasks map directly to Salesforce Tasks with subject, status, priority, due date, and description fields preserved. Owner assignment resolves by email match against Salesforce User records for accurate user attribution. Tasks linked to specific Cases in ArkCase maintain their WhatId reference to the migrated Salesforce Case record to preserve the task-to-case relationship.

ArkCase document attachments download from the ArkCase ECM integration (SharePoint, Alfresco, or ArkCase native file store) and re-upload as Salesforce Files. Each file becomes a ContentVersion linked to the parent Case or Contact via ContentDocumentLink. ArkCase file version history is preserved as a custom field on the ContentVersion record.

ArkCase case participants (Complainant, Respondent, Attorney, Witness) associated with a case are mapped to Contacts and linked via CaseContactRelation. If a participant has multiple roles across cases, all roles are preserved as separate CaseContactRelation records with the appropriate role value.

Every ArkCase custom property defined on Case objects requires a corresponding Salesforce custom field. We create the field in Salesforce (with __c API name suffix), set the correct data type (text, picklist, date, number), and map the property value during migration. Custom properties with pick-list values require value-by-value mapping to the Salesforce pick-list options.

ArkCase custom properties on Person objects become Salesforce custom fields on Contact. Type-aware mapping applies: date properties to Date fields, numeric properties to Number fields, and free-text properties to Text fields. Multi-select pick-lists in ArkCase map to Salesforce multi-select pick-lists.

ArkCase custom objects (defined via the ArkCase REST API data model) map 1:1 to Salesforce custom objects. Custom object records migrate with all standard and custom fields. N:N relationships between custom objects in ArkCase require Salesforce custom junction objects, which we create as part of the schema plan.

ArkCase BPMN 2.0 workflow definitions (task routing, approval chains, automated actions) have no direct Salesforce equivalent. We export ArkCase workflow definitions as process documentation for your Salesforce admin to reference when building Flow. The workflow logic itself cannot be migrated automatically.