Migrate from Antura to Trello

Antura Projects map to Trello Boards. Each Antura project name becomes a Trello board name, project status (active, on-hold, completed) maps to board archiving or list status, start and end dates map to optional board description fields or Power-Up timeline data. We create boards in Trello via the Trello REST API, preserving project owner as a board member with Admin role. Portfolio membership does not map natively; we flag this as a Workspace organizational strategy that the customer configures post-migration.

Antura Sub-projects nested under parent Projects map either to separate Trello Boards linked via board description or external URL, or to top-level Lists within the parent Board. We discuss the preferred strategy during scoping: separate boards preserve sub-project independence but lose visual hierarchy; lists within a board preserve the hierarchy but require list naming conventions to distinguish sub-project boundaries. Sub-project status, dates, and owner migrate in either case.

Antura Tasks map to Trello Cards with task name as card title, description as card description, assignee as card member, due date as card due date, and status as card list position or a custom status field. Antura's flat task hierarchy (no native subtask nesting) maps cleanly to Trello's flat card model. For any customer-specific subtask conventions captured as custom fields, we map to Trello checklists within the parent card, noting that checklist items cannot have independent assignees, due dates, or attachments unlike full Trello cards.

Antura Resources represent employees with name, email, capacity, skills, and cost rates. We extract the resource list from Antura's export and provision Trello Workspace members by email invite. Resource capacity percentages and cost rates have no native Trello field; we migrate these as custom fields on a per-board administrative card or as a custom field Power-Up setup post-migration. Utilization reporting that Antura provides natively requires Trello Premium with a reporting Power-Up such as Screenful.

Antura Milestones are date-driven markers within Projects. Trello has no native milestone construct. We map milestones to dedicated Trello Cards with the milestone name as title, the milestone date as card due date, and a distinct Label (e.g., 'Milestone') to visually separate milestone markers from regular tasks. Customers on Trello Premium can use the Timeline view to visualize milestone cards as date ranges. We document this mapping strategy during scoping and note that milestone dependency tracking does not transfer.

Antura Risks and Issues tracked as separate objects with severity, probability, owner, status, and mitigation fields map to Trello Cards with a 'Risk' or 'Issue' Label, severity and probability stored as custom dropdown or number fields, and mitigation text stored in the card description. Trello's lack of a dedicated risk register means these records lose the structured risk-specific views (risk matrix, probability-impact grid) that Antura provides. We migrate the data and flag the visualization gap in our written inventory.

Antura Cost Records include budget estimates, actuals, and forecasts per Project. Trello has no native financial fields. We map cost data to number-type custom fields on an administrative card within the project board (estimated budget, actual spend, variance) or to Trello Premium custom fields at the card level if cost tracking is needed per-task. Multi-currency handling requires the customer to standardize to a single currency before migration or to store currency metadata alongside numeric values. We flag that native cost reporting does not exist in Trello and recommend a Power-Up or external BI tool for ongoing financial visibility.

Antura Time Entries record hours by Resource on Tasks or Projects with date, duration, and description. Trello has no native time-tracking object. We map time entries either as checklist items on the relevant Card (with hours recorded as text in the checklist item) or as number custom fields on Cards if Trello Premium custom fields are available. For organizations with significant time tracking requirements, we recommend a time-tracking Power-Up (such as a Time Tracking Power-Up or a third-party integration) as a post-migration configuration step.

Antura allows organization-specific custom fields across Projects, Tasks, and Resources with no public metadata API for schema discovery. We handle this by including a schema discovery phase where we export a full field inventory from the customer's Antura instance through the CSV export process, identify Swedish-language field labels, and map each to the equivalent Trello custom field type. Trello supports five custom field types: Number, Date, Dropdown, Checkbox, and Text. Custom fields on the Free plan require a Power-Up; Standard and Premium include custom fields natively. We confirm the customer's Trello plan tier during scoping.

Antura Documents attach to Projects and Sub-projects as binary files. We extract document metadata (name, type, date, owner) from Antura's export but cannot transfer actual file binaries through standard data migration methods. We provide a file inventory document listing every Antura document with its project, file type, and storage location (path in Antura's document management area). The customer runs Antura's document bulk export to a shared network location or cloud storage, and reattaches files to the corresponding Trello Cards post-migration. We do not handle the file transfer itself.

Antura Portfolios group Projects for strategic oversight with priority, status, and strategic alignment metadata. Trello has no Portfolio construct. We map portfolio membership to Trello Workspace structure: each Antura Portfolio becomes a Trello Workspace (available on Standard and Premium plans; Free plan uses a single default Workspace), and Antura Projects within that Portfolio become Boards within the Workspace. Portfolio-level priority and strategic alignment metadata migrates as custom fields on an administrative board within the Workspace. We confirm the customer's Trello plan tier during scoping because the Free plan restricts Workspace creation.

Antura stores task-level activity history including comments, file attachments, and status change logs. Trello Cards have a native activity feed and support attachments. We extract activity records from Antura's CSV export, parse comment text and timestamps, and inject them into Trello Card comment fields via the Trello API. File attachments on tasks map to Trello Card attachments. We note that Antura's detailed activity log structure (e.g., separate entries for status changes vs. comments) flattens into Trello's chronological comment feed, which is a loss of granularity that we document in the written inventory.