Migrate your ArkCase data

Cases are the primary container object in ArkCase. They hold nested documents, task lists, complaint links, and full audit history. We export cases as structured JSON bundles including all related child records and preserve the case status and assignee during the import into the destination system.

Complaints are a distinct object type that can be linked to Cases or stand alone. They carry their own lifecycle, fee-waiver flags, litigation flags, and expedite flags. We map complaint status transitions directly to the destination's equivalent status field or raise a mapping flag if no equivalent exists.

Tasks are associated with Cases, Complaints, or other parent objects. Each task has an assignee, due date, priority, and completion status. We preserve the task-parent relationship during migration and flag any orphaned tasks that lose their parent reference in the destination.

Documents are stored with version chains, check-in/check-out flags, and classification metadata. We export the full binary blob, version history, and access-control metadata. OCR-extracted text is stored as a companion record and migrates alongside the document.

ArkCase workflows are defined in BPMN 2.0 XML and executed by an embedded workflow engine. Custom drag-and-drop workflows are stored as process definitions. We export the XML definitions but rebuilding the same automation logic in a destination BPMN engine requires manual review — we provide the exported XML plus a task-by-task human-readable summary.

Time and expense records are linked to Cases, Complaints, or Tasks. Each entry carries hours, a billing rate, and a cost code. We export time entries as line items with their parent object reference and preserve the person who logged the time.

ArkCase uses LDAP and directory-service integration for identity. Role-based access controls are defined within the platform. We export user accounts and role assignments but cannot migrate LDAP group memberships directly — those must be re-established in the destination directory service.

ArkCase supports extended custom fields on most objects. These are defined in the data model schema. We export the full custom-property set per record but flag any property that has no corresponding field in the destination schema, requiring a manual field-creation step before import.

FOIA requests are a specialised object type with specific lifecycle stages (received, in-progress, responsive-materials, closed). We preserve the request, its associated documents, and status flags. Stage names vary by jurisdiction — we document the source-stage values and map them to destination equivalents during the transfer.

ArkCase maintains a comprehensive audit log for all object changes. We export audit entries as a time-ordered event stream. Most destination systems do not have a native audit-stream object, so we import audit records as a structured log file or custom object rather than native audit records.