Migrate your Kantata Professional Services Cloud (formerly Mavenlink + Kimble) data

Workspaces are the primary project container in Kantata OX. They carry status, dates, budget fields, billing information, and an activity feed. We extract the full workspace record including archived ones and preserve the workspace/project hierarchy intact in the destination.

Tasks (OX) and Stories (OX) share the same underlying object. They support nesting via parent-child relationships, WBS numbering in the New Task Tracker, and custom field attachments. We preserve task hierarchy, assignees, status, and custom field values during migration.

Subtasks attach to parent tasks and inherit some parent-level fields. The WBS numbering in the New Task Tracker can misfire when multiple subtask levels are nested. We flag deeply nested subtask chains during scoping and normalize the structure if the destination lacks native subtask support.

Users represent internal staff and contractors with role assignments, permission settings, and contact details. We map active users to their destination equivalents and flag inactive or archived users for explicit handling.

Assignments link a User to a Task within a Workspace and carry hours allocated, role, and billing rate. Rate precision and effective date handling vary between OX and SX. We capture the assignment graph and remap role-based rates against the destination's billing structure.

Time entries record billable or non-billable hours against a task or project, with date, user, and notes. The Weekly Schedule View lets users copy allocated hours to timesheets in bulk. We export full time entry history and associate each entry to its target object in the destination.

Estimates model supply-and-demand scenarios using role-based resource composition and margin projections. Scenarios are versioned within the same workspace. We extract all active and historical scenarios and map role-based line items to the destination's quoting or estimating object.

Custom fields are organized into sets scoped by subject_type (Estimate, Story, User, Workspace, WorkspaceGroup, Resource). Custom Fields and Custom Field Values are separate API objects with independent rate limits. We extract the full field definition including field type, choice options, and read_access permissions, then migrate values in subject_type batches.

Billing allows multiple invoices during a project's lifetime. Financial data—billing rates, milestone invoices, and expense charges—is tightly coupled to the workspace and resource assignment records. We export invoice history and line items and map them to the destination's accounts receivable or billing module.

Groups organize workspaces into folders or portfolios and carry their own custom fields. Group-level custom field values require a separate API call scoped to WorkspaceGroup. We extract group hierarchies and group-level custom data as a distinct migration pass.

External references link Kantata records to objects in external systems (e.g., Salesforce for SX). The API supports filtering by external_reference_service_model, external_message, and external_status. We preserve external reference IDs so downstream integrations remain functional post-migration.

File attachments live in the collaboration workspace and the activity feed. Attachment URLs are accessible via the API but file size limits and storage quotas are set per workspace tier. We flag attachment-heavy workspaces early to account for volume-based export throttling.