Migrate from ArkCase to Pipedrive

ArkCase Person maps 1:1 to Pipedrive Person. All standard contact fields (name, email, phone, job title, address) transfer directly. The ArkCase Person–Organization link migrates as the Pipedrive primary OrganizationId lookup — one primary org per person, consistent with Pipedrive's data model.

ArkCase Organization maps 1:1 to Pipedrive Organization. Org name, address, domain, industry, and employee count transfer as direct fields. Parent–child org hierarchies in ArkCase map to Pipedrive's parent_org_id field. Multi-party affiliations require one primary org per person with secondary affiliations surfaced as custom text fields.

ArkCase Case has no native Pipedrive equivalent — Cases migrate as Pipedrive Deals with a custom custom_case_number__c text field (max 255 chars) to preserve the original case reference ID. Case status (e.g., Open, Pending, Closed) maps to a custom status pick-list on the Deal. Priority, category, and assigned_team fields become custom fields on the Deal record.

ArkCase Case–Person associations (e.g., case initiator, case contact, case assignee) map to Pipedrive's Person–Deal association. In Pipedrive, each Deal can link multiple Persons with a designated 'main' contact flag. ArkCase's role label on the association (e.g., Requester, Assignee) migrates as a custom pick-list field on the Deal's person link.

ArkCase Complaint object has no Pipedrive equivalent. Complaints migrate as Deals with a custom complaint_type__c field and custom is_complaint__c boolean flag. If the complaint relates to an existing Person or Organization, the Deal links to that record; standalone complaints become Deals without a linked Organization.

ArkCase Tasks map to Pipedrive Activities with type='task'. Original due dates, assignees, and completion status transfer. ArkCase task checklists (sub-task lists) cannot migrate as nested structures in Pipedrive — we flatten them into individual Activity records linked by a custom parent_task__c field.

ArkCase documents (versions, ACL metadata, check-in/check-out state) are flattened to Pipedrive Files attached to the mapped Deal or Person. Version history is captured as a custom versions__c text field. Files exceeding Pipedrive's 25MB limit are flagged and can be stored externally with a URL custom field linking back to the original ArkCase repository.

ArkCase custom objects migrate as Deal custom fields if they hold scalar values (text, number, date, pick-list). Complex nested ArkCase custom objects with their own sub-relationships migrate as formatted notes on the parent Deal or Person, preserving the JSON payload in a custom custom_object_payload__c field for future parsing.

ArkCase users are matched to Pipedrive users by email address. Unmatched users are flagged before migration — the team either creates Pipedrive accounts first or assigns records to a designated fallback owner. ArkCase role names (e.g., Case Manager, Reviewer) cannot map to Pipedrive roles and must be stored as a custom field on the record.

ArkCase's per-record audit trail (status changes, assignment changes, document additions) has no native Pipedrive equivalent. We export the audit log as a JSON blob stored in a custom audit_log__c long-text field on the Deal. If audit log length exceeds the 32,768-character limit, we truncate and flag for manual retrieval.

ArkCase BPMN 2.0 workflows do not migrate. We export each workflow definition as a JSON file with trigger events, gateway conditions, and action steps documented. Pipedrive Automations use a trigger-action model (no BPMN gateway support) — your Pipedrive admin uses the exported workflow JSON as a rebuild specification.

ArkCase's fine-grained object-level and document-level ACLs have no Pipedrive equivalent. We map ArkCase role names to Pipedrive visibility groups by name where possible. Document-level permissions are lost — we add a custom original_acl__c text field storing the original ArkCase permission summary for audit reference.