Migrate from Moovila to Asana

Moovila Projects map to Asana Projects with project name, description, start date, target end date, status (active, on-hold, completed), budget, and owner assignment preserved. Template-derived projects retain their base structure; we migrate the project with its task hierarchy and mark the originating template in a custom field. Projects that were paused or archived migrate with their status preserved so the customer's team can decide whether to activate or archive in Asana.

Moovila Tasks and subtasks map to Asana Tasks with hierarchy intact. We preserve task name, description (rich text), status, assigned owners (resolved via User mapping), due dates, start dates (mapped to Custom Fields in Asana Free/Premium; native Start Date from Business tier), and completion status. Moovila's task acceptance/rejection fields migrate as custom fields. Nested task depth up to five levels is preserved as subtasks within subtasks.

Moovila Milestones map to Asana Milestones on the Timeline. Milestone name, target date, and linked tasks migrate. The milestone-to-task linkage is preserved by adding a milestone association to the relevant Asana task. Milestones that anchored Moovila's critical path calculations are preserved as timeline markers so the customer's team can use Asana's Timeline dependency view to re-establish critical path visibility.

Moovila's finish-to-start, start-to-start, finish-to-finish, and start-to-finish dependency types map to Asana's dependency field (which supports finish-to-start and start-to-start natively, with the others handled as offset custom fields). We preserve the predecessor-successor relationship by task GID lookup and set the dependency type during migration. Large dependency graphs (over 50,000 links) require batching under Asana's API rate limits.

Moovila base templates and mini-templates map to Asana project templates if the destination is on Business tier, or to Projects with a template-origin custom field on Free and Premium. Template task structures, milestones, and resource placeholders migrate as project elements. Template analytics data (performance benchmarks per template) does not migrate because Asana does not have a template analytics equivalent; we document the existing analytics as a CSV export for the customer's reference.

Moovila Resources (individuals, roles, enterprise-level cost rates) map to Asana User records. We resolve Moovila resource assignments by matching the Moovila resource email or name to the Asana User table. Role-level resources without an associated user account are held in a reconciliation queue; the customer's admin provisions user accounts before these assignments are finalized. Utilization targets and resource demand data migrate as custom fields on the relevant tasks.

Moovila User accounts map to Asana Users with email, display name, and security role preserved. Moovila Teams (unlimited on Business tier) map to Asana Teams. Extended Viewers and Editors from Moovila Business tier are preserved as Asana Team membership with the appropriate permissions. SSO and domain management settings are documented as configuration notes for the customer's admin to re-configure in Asana Admin settings.

Moovila time submissions, hours, dates, and billing codes are available on Business and Enterprise tiers only. We check the customer's Moovila tier during scoping; Pro-tier accounts have no time entry data and this object is excluded. For Business and Enterprise accounts, time entries migrate as task-level custom numeric fields (hours logged per task) and billing codes migrate as custom fields. Asana's native time tracking is a Business-tier feature; we map time entry data into Asana custom fields or a time tracking tool integration depending on the customer's destination tier.

Cost codes, billing codes, and rate schedules from Moovila Business and Enterprise tiers migrate as Asana custom fields on projects and tasks. These are text or numeric custom fields that preserve the original Moovila code and rate values. Customers should verify whether Asana's destination tier supports the number of custom fields needed for their billing code schema; Asana Free allows 15 custom fields per project, Premium allows 100 per project, and Business allows unlimited.

Moovila Project Risk Registers, including manually entered risks and risk status, severity, and mitigation notes, migrate as Asana custom fields on the relevant project or as dedicated tasks tagged with a Risk label. AI-generated risk predictions from Moovila's RPAX engine do not migrate because they are computed at runtime and not stored as persistent data fields. We flag the risk register during scoping and advise the customer that Asana's native reporting and any installed risk management app will generate fresh risk views from the imported task and dependency data.

Moovila project-level notes (stored in a dedicated notes register) migrate to Asana Notes on the project. Moovila task-level comments migrate as Asana Task comments with author and timestamp preserved. Integrated chat channel threads migrate as comment threads on the associated project or task. We preserve the created_at timestamp and author attribution where available from the Moovila API.

Moovila project and task attachments reference Box, Dropbox, SharePoint, OneDrive, and Google Drive files via cloud storage integration links. We migrate the attachment reference URL and filename, preserving the original file link. Actual file content is not re-uploaded; the customer ensures the linked cloud storage remains accessible. File attachments exceeding Asana's 100MB limit per file are flagged and excluded from the migration scope.