Migrate from Antura to Microsoft Project

Antura Project records map to Microsoft Project files (MPP) or Project Online Project entities. We preserve Project Name, Status, Start Date, Finish Date, Description, Project Manager (Owner), Budget, and custom fields. The destination project is created before any child records load so that Task-Project relationships resolve correctly during import.

Antura Sub-projects nest under parent Projects with their own milestone and task sets. Microsoft Project does not have a native Sub-project construct; instead we map Sub-projects to Summary Tasks with indented child tasks, preserving the hierarchy by setting Summary Task = True on the parent task row. Task names, dates, and durations map directly.

Antura Tasks in a flat structure under Projects map to Microsoft Project Task records. We preserve Task Name, Start, Finish, Duration, Percent Complete, Priority, Description, and Assignee. Dependency relationships in Antura (Finish-to-Start, Start-to-Start) map to Microsoft Project predecessor links. Antura's flat task model means any implied parent-child relationships must be reconstructed from Antura's WBS column if the customer uses hierarchical numbering.

Antura Milestones are date-driven markers with optional descriptions. Microsoft Project Milestones are tasks with zero duration marked as Milestone = True. We preserve milestone name and date, mapping to the equivalent milestone task in the destination project file.

Antura Resources (employees with capacity, skills, and cost rates) map to Microsoft Project Resources. We preserve Resource Name, Type (Work or Material), Max Units (capacity percentage), Standard Rate, Cost Per Use, and accrual method. Resource Groups in Antura map to Microsoft Project Resource Groups. If Antura resources have skill associations, these map to custom resource fields in Microsoft Project.

Antura resource allocations linked to Tasks map to Microsoft Project Assignments with Work (hours) and Units (allocation percentage). We resolve the resource reference using the name-to-resource mapping and set Assignment Owner to the matching Microsoft Project resource row. Utilization percentages migrate to Assignment Units.

Antura Risks and Issues are tracked as separate objects with Severity, Probability, Owner, Description, and Mitigation fields. Microsoft Project stores Risks as custom fields on the project or as SharePoint Lists linked to the project; Issues are tracked similarly. We map to a custom Issue/Risk section in the MPP file or a SharePoint list if the destination is Project Online, preserving severity and owner as custom fields.

Antura Time Entries record hours spent by Resources on Tasks with date and description. We map these to Microsoft Project Actual Work on Task Assignments, setting Actual Work and Actual Start/Finish from the time entry date and hours. Billable rate preservation requires matching the Antura cost rate to the Microsoft Project Resource Standard Rate in the resource mapping.

Antura Cost Records include estimates, budgets, actuals, and forecasts per Project with cost types and accounts. We map budget values to Microsoft Project Fixed Cost and Per Use Cost fields on Tasks, and project-level budgets to the Project Summary Task or a custom cost field. Multi-currency handling requires setting the destination project currency before cost data loads.

Antura Portfolios group Projects with priority, status, and strategic alignment fields. Microsoft Project Online uses Project Center for a flat project list and Roadmap (Planner Premium) for cross-project portfolio views. We map portfolio membership and priority to the Project Center view metadata and create Roadmap items in Planner Premium if the customer has that license. Strategic alignment notes migrate as a custom Project field.

Antura allows organization-specific custom fields on Projects, Tasks, and Resources. During scoping we manually discover the active custom field set through Antura's admin interface because there is no metadata API. Each discovered custom field is mirrored as a custom field in Microsoft Project (Text, Number, Date, Flag, or Lookup depending on the Antura field type). If the destination is Project Online, enterprise custom fields are provisioned in the PWA settings before data import.

Antura Documents attach to Projects and Sub-projects as binary files. We extract document metadata (name, type, date, owner, size) and map to a SharePoint Document Library if the destination is Project Online or to a local folder reference if the destination is Microsoft Project desktop. Actual binary file transfer is handled separately via Antura's document export feature to a shared location, with manual reattachment at the destination.