Migrate from Kantata Professional Services Cloud (formerly Mavenlink + Kimble) to Trello

Kantata Workspaces (OX) and the equivalent project container in SX map to Trello Boards. The workspace name becomes the board title. We preserve the workspace description as the board description, workspace status (active, on hold, completed) as a Trello Label or custom field, and the created date as the board creation date. Workspace color coding in Kantata maps to Trello Labels with a color match where feasible. Archived workspaces do not migrate as active boards but are listed in the migration report for manual Trello board archival if needed.

Kantata Stories (OX) and equivalent task items map to Trello Cards. The story title becomes the card title. The story description migrades as the card description with Markdown formatting preserved. Due dates on stories map to card due dates. Story status (todo, in progress, complete) maps to card position within Trello Lists (To Do, Doing, Done) or to custom field values if the customer uses a different List structure. Assignee resolution matches the Kantata user email to a Trello Workspace member; unassigned stories create unassigned cards with a note in the migration report.

Kantata Tasks (distinct from Stories in some workspace configurations) map to Trello Cards using the same mapping logic as Stories. Parent-child task relationships do not have a native Trello equivalent. We flatten the hierarchy by nesting child task titles within the parent card description as a structured Markdown list, preserving the relationship for admin review. Deeply nested subtask hierarchies with WBS numbering are flagged in the migration report since Kantata's own New Task Tracker has a documented WBS display bug in multi-level subtask chains.

Kantata Subtasks attach to parent Tasks or Stories and inherit some parent-level fields. We convert each subtask to a Trello Checklist item on the parent Card, preserving the subtask title, completion status, and assigned user if present. Subtasks with due dates are marked with the due date in the checklist item title. Since Trello does not support nested checklists or subtask-level checklists, deeply nested subtask chains are flattened to a single checklist level with a prefix indicating hierarchy depth.

Kantata Users (internal staff and contractors) map to Trello Workspace members by email address. We extract the user's display name, email, role in Kantata, and active/inactive status. Active Kantata users are invited to the Trello Workspace during migration; inactive or archived users are documented in the reconciliation report. Role information does not have a native Trello equivalent and is stored as a custom field on the member profile or in the migration report for admin mapping to Trello Workspace roles on Enterprise plans.

Kantata time entries record billable or non-billable hours against a task or project with date, user, duration, and notes. Trello has no native time-tracking object. We migrate time entry summaries as a structured custom field on the relevant Card (total hours logged, total billable hours) with the most recent time entry date noted. If the customer requires granular time entry history, we document the full set of time entries in a CSV export alongside the migration and recommend a Trello Power-Up (such as Card Timer, Time Tracker, or Planyo) as the post-migration time-tracking layer.

Kantata Resource Assignments link a User to a Task within a Workspace carrying hours allocated, role, and billing rate. Trello Cards support a single assignee or multiple assignees but do not carry role or billing rate information. We map the primary assigned user from the Resource Assignment to the Card assignee. Role and billing rate data are flagged in the migration report as fields that cannot be represented in Trello; the customer admin decides whether to store role as a custom field on Cards or handle resource rate data outside Trello.

Kantata Estimates model supply-and-demand scenarios using role-based resource composition and margin projections. Scenarios are versioned within the same workspace. Trello has no native estimation or scenario modeling capability. We extract active and historical scenario records to a structured JSON export and migrate the most recent estimate hours and budget values as custom fields on the relevant Board or Card. Scenario comparison and margin forecasting are documented for manual rebuild using a spreadsheet or a dedicated estimation tool post-migration.

Kantata Custom Fields are scoped by subject_type (Estimate, Story, User, Workspace, WorkspaceGroup, Resource) and exposed as separate API objects from their values. Trello Standard and Premium support custom fields on Cards with types including text, number, date, checkbox, single-select, multi-select, and member. We map each Kantata custom field value to the equivalent Trello custom field on the migrated Card. Fields that do not have a matching Trello type (for example, complex structured data or formula fields) are stored as text custom fields. Subject-type scoping is documented per Card in the migration report.

Kantata WorkspaceGroups organize workspaces into folders or portfolios and carry their own custom fields. Trello has Workspaces as the top-level organizational unit but no native equivalent to Groups for nesting boards. We create separate Trello Workspaces for major WorkspaceGroup collections or document the grouping structure for manual organization into Trello Workspace sections. Group-level custom field values require a separate API call scoped to WorkspaceGroup in Kantata; we include these in the extraction and map them to the top-level Board where applicable.

Kantata billing allows multiple invoices during a project lifetime with financial data tied to workspace and resource assignment records. Trello has no billing or accounts receivable object model. We do not migrate billing records into Trello. Instead, we extract invoice data to a structured CSV export including invoice number, date, amount, line items, and linked project reference, and deliver this alongside the migration. The customer admin reconciles billing data with their accounting system post-migration.

Kantata file attachments live in the collaboration workspace and activity feed with per-workspace storage quotas. We extract attachment metadata (filename, URL, file size, upload date) and migrate the attachment references as external links on the relevant Trello Card. If the attachment URL is still accessible via Kantata's API after migration, we preserve the link. Large file attachments that exceed Trello's attachment limits or that the customer wishes to migrate to a dedicated cloud storage (Google Drive, SharePoint, Confluence) are documented with the full URL for manual re-link post-migration.