Migrate from Antura to monday Work Management

Antura Projects map directly to monday.com Boards. We preserve project status workflow, dates, budgets, and responsible owners as board metadata and configuration. The board name comes from the Antura project name, and we set the board's workspace during import based on whether the Antura project belongs to a portfolio group.

Antura Sub-projects nest under parent Projects and inherit portfolio-level metadata. We map these to monday.com Groups within the parent Board, preserving the sub-project name, status, dates, and owner as group-level column data. The parent-child relationship is maintained by placing both in the same Board with the parent Project as the board root.

Antura Tasks map to monday.com Board Items. We preserve task status, assignees, dates, and descriptions as typed columns in the destination board. Antura's flat task structure under Projects means we do not encounter subtask nesting; any parent-child task relationships in Antura require manual flagging during scoping because monday.com Groups do not support hierarchical item nesting natively.

Antura Resources represent employees with capacity data, skills, and cost rates. We map the resource name and email to monday.com's Person column type. Capacity percentages and utilization data have no native monday.com equivalent; we create formula columns or numeric columns to capture utilization percentages, and note that cost rate fields require a numeric column with manual configuration since monday.com lacks a native cost-rate field type.

Antura Resource Allocations link a Resource to a Project with an allocation percentage. We preserve these as Person column assignments (the resource) paired with a numeric column (the percentage) on each board item representing the work package. This is a configuration workaround because monday.com has no native allocation object.

Antura Risks track severity, probability, owner, and mitigation fields. We map these to monday.com Board Items using status, numeric, and person columns for the risk attributes. The risk description and mitigation notes map to a text column. We flag that monday.com has no native risk object, so risk data lives alongside project items on the same board and may require a separate board for organizations with dedicated risk registers.

Antura Issues share a similar structure to Risks with severity, owner, and status fields. We map Issues to monday.com Board Items identically to Risks, using status columns for issue state and priority, person columns for the assigned owner, and text columns for the issue description and resolution notes.

Antura Milestones are date-driven markers within Projects with optional description fields. We map milestone dates to monday.com Date columns and milestone names to a text column. Multiple milestones per project may require a dedicated sub-board or a milestone-tracking column set because monday.com treats milestones as date markers rather than discrete objects.

Antura Portfolios group Projects for strategic oversight with priority, status, and strategic alignment fields. Monday.com has no native portfolio hierarchy; we flatten the structure by creating a Workspace per Antura Portfolio and placing project boards within that workspace. Portfolio-level priority and strategic alignment fields migrate to a metadata board or text columns on individual project boards.

Antura Cost records include estimates, budgets, actuals, and forecasts per Project. We map these to monday.com numeric columns for budget, actual, and variance tracking. Multi-currency handling requires exchange rate configuration at migration time and we note that monday.com does not support native multi-currency; the customer configures currency display at the account level before migration begins.

Antura Time Entries record hours spent by Resources on Tasks or Projects with date and description. We map these to monday.com items using the date column for the entry date, a number column for hours, and the person column for the resource. Note that monday.com's native time tracking (available on Pro and above) is item-level rather than cross-project; organizations with complex time tracking needs may require a separate time-tracking board as a workaround.

Antura supports organization-specific custom fields across Projects, Tasks, and Resources. We discover the active custom field schema during scoping by exporting field lists from Antura's admin interface, then map each to monday.com column types: text fields to Text columns, numeric fields to Number columns, date fields to Date columns, and dropdown fields to monday.com Status or Dropdown columns. The mapping is board-specific because monday.com columns are defined per board rather than organization-wide.