Migrate from Antura to Asana

Antura Projects map to Asana Projects with project name, description, start date, due date, status, and owner preserved. Antura's project status workflows map to Asana project status indicators (on track, at risk, off track). Owner resolution happens via email match against Asana workspace members; any owner without a matching Asana user enters a reconciliation queue for the customer's admin to provision before record import.

Antura Sub-projects map to Asana Projects nested under the parent Project, or to Asana Sections if the customer prefers a flatter structure. We resolve the parent-child relationship using Antura's project hierarchy export and create either sub-Projects or Sections based on the customer's scoping preference. Sub-project metadata (dates, budget, owner) map to the destination project fields.

Antura Tasks map to Asana Tasks with title, description, assignee, start date, due date, and status preserved. Antura's flat task structure maps directly to Asana's task model. Any task flagged as a milestone in Antura maps to an Asana Milestone (Premium+ required). Tasks without an assignee in Antura become unassigned tasks in Asana; we preserve the original task owner in a custom field antura_owner__c for audit.

Antura Milestones map to Asana Milestones on Premium tier and above. Milestone dates and names migrate directly. Antura milestones without a linked project map to a default Asana project designated during scoping. Note that Asana does not support milestones on the Free plan; we flag this and recommend upgrading to Premium or placing milestones in a separate tracking project on lower tiers.

Antura Resources (employees with capacity, skills, cost rates, and utilization) map to Asana workspace members. We extract the Antura resource list and match by email address to Asana users. Capacity and utilization percentages migrate to a custom field resource_capacity__c on the user's Asana profile or to a custom project-level field. Cost rates migrate to a custom field cost_rate__c. Skills migrate to a multi-select picklist custom field skills__c if the customer requests it during scoping.

Antura Time Entries (hours, date, description linked to Tasks or Projects) map to Asana Tasks with time entries. On Asana Premium and above, we use Asana's native time tracking feature to log hours against tasks. On lower tiers, we create a custom time_tracked_hours__c numeric field and a time_entry_date__c date field per task, with a separate Time Entries report delivered as a CSV for the customer's admin to import into a time-tracking integration like Toggl or Harvest post-migration.

Antura Risks (severity, probability, owner, mitigation fields) map to Asana Tasks with a risk_type__c custom field set to 'Risk'. Risk severity maps to priority (high = urgent, medium = high, low = normal). Probability percentage maps to risk_probability__c custom field. Mitigation description migrates to the task description with a 'Mitigation' section. We recommend a dedicated Asana project for risk tracking so risks aggregate in a single portfolio view.

Antura Issues (severity, owner, description fields) map to Asana Tasks with an issue_type__c custom field set to 'Issue'. Issue severity maps to priority. The original Antura issue description migrates to the task description. Issues and Risks split into separate task types so the customer can filter by type in Asana's project views.

Antura Portfolios (grouping Projects with priority, status, and strategic alignment) map to Asana Portfolios on Business tier ($24.99/user/month). On lower tiers, we map portfolio membership to Asana Teams with a naming convention (e.g., 'Portfolio - Strategic Initiatives') and add a portfolio_priority__c custom field to each project. Strategic alignment fields map to a custom field strategic_alignment__c text field. We recommend the Business tier for organizations that rely heavily on portfolio-level reporting.

Antura Cost Records (estimates, budgets, actuals, forecasts per Project) map to numeric custom fields on the Asana Project: cost_estimate__c, cost_budget__c, cost_actual__c, cost_forecast__c. Multi-currency handling requires the customer to confirm their Asana workspace currency setting during scoping; we note that Asana does not natively support multi-currency so conversions use the exchange rate at migration date.

Antura Document metadata (name, type, date, owner) migrates to a document registry CSV delivered to the customer. Actual binary files cannot transfer through standard data migration methods because Antura stores documents as binary attachments without a documented file access API. We recommend the customer export documents from Antura to a shared cloud location (Google Drive, SharePoint, Dropbox) and reattach them to Asana tasks post-migration. We provide a document mapping table linking Antura document IDs to Asana task targets.

Antura custom fields (organization-specific fields on Projects, Tasks, and Resources) require a discovery phase before migration because Antura has no public metadata API for external schema introspection. We guide the customer through a full custom field export from Antura's admin interface, map each field to an Asana custom field, and configure custom field settings per project in Asana. Field types (text, number, date, dropdown, checkbox) map to Asana custom field types. Any custom field without a clear Asana equivalent enters a mapping exception list for the customer's admin to resolve.