Migrate from Agilean to Asana

Agilean Projects map to Asana Projects. We enumerate all active and archived projects during discovery, preserve the project name, description, and any start/end dates. Project-level permissions in Agilean map to Asana team membership and project sharing settings. Agilean projects that contain no tasks are migrated as empty Asana projects for structural completeness; the customer decides whether to activate or archive them in Asana after migration.

Agilean Tasks map to Asana Tasks. Task name, description (migrated as rich text), assignee (resolved by email to Asana User), due date, and status map directly. We preserve subtask hierarchy by creating Asana Subtasks under their parent Task. Sections in Agilean migrate as Asana Sections within the parent Project. Task-level custom fields migrate as Asana Custom Fields on the task (see Custom Field mapping for type-matching details). Historical created_at and modified_at timestamps preserve via Asana API.

Agilean custom fields migrate to Asana Custom Fields, but type-matching is enforced: Agilean text fields map to Asana text, numeric fields to number, date fields to date, and multi-value fields to multi-select picklist. Asana requires that form question types correspond to custom field types, so if an Agilean custom field has a type that Asana does not support (e.g., a complex conditional field), we map it to a text field and note the deviation for the customer's admin to refine post-migration. Custom fields with the same name as existing Asana portfolio-level fields receive a deconfliction prefix per Asana's naming policy.

Agilean file attachments migrate to Asana Attachments. We extract attachment metadata (filename, size, content type, URL or file blob) and attach each to the corresponding migrated task via the Asana Attachments API. Attachments are uploaded in the same sequence as their parent tasks to avoid orphaned references. If an Agilean attachment references a URL that is no longer accessible, we flag it in the reconciliation report and note it in the handoff documentation.

Agilean Notes attached to tasks or projects migrate as Asana Notes (or Comments, depending on whether the note is a standalone note object or a threaded comment in Agilean). We map the note body as rich text and link it to the parent task via the Asana Stories or Notes API. Timestamps from the original Agilean note are preserved in the Asana note's created_at field.

Agilean workflow configurations (triggers, conditions, and automated actions scoped per consulting engagement) do not migrate as executable code. We deliver a written inventory of every active workflow configuration, documenting its trigger, conditions, actions, and the recommended Asana Rules equivalent. The customer's admin rebuilds Rules in Asana's Rules engine, which uses a trigger-action model that differs structurally from Agilean's configuration-driven approach. Workflow rebuild is outside the standard migration scope.

Agilean project templates (reusable task structures and workflow patterns) migrate as documented Asana project templates if Agilean exports them as reusable artifacts. If templates are embedded in individual projects rather than as shareable objects, we deliver a template inventory document describing each project's task structure, section layout, and field schema so the customer's admin can replicate them as Asana templates manually or via Asana's template API.

Agilean user accounts map to Asana Users by email address. We enumerate all active Agilean users during discovery and match them against the target Asana workspace membership. Any Agilean user without an Asana account goes to the provisioning queue; the customer's admin provisions the Asana account before the user-specific migration phase begins. User-level permissions (admin, member, guest) map to Asana's role model.

Agilean tags or labels attached to tasks migrate as Asana Tags. Tags are preserved as free-form labels without a type constraint, allowing the customer's team to organize and filter by tag in Asana's tag-based views. If Agilean uses tags for status (rather than classification), we note this in the inventory so the admin can decide whether to convert tag-based status to Asana's built-in Custom Fields status workflow.

Agilean time tracking entries (if present) migrate as Asana time tracking entries attached to the corresponding task. Asana's native time tracking is available on Business and Enterprise tiers; Starter and Premium tiers use third-party integrations. We confirm the customer's Asana tier during scoping and either migrate to native time tracking or map to a custom field capturing duration for lower tiers.

Agilean portfolio or program-level groupings (if used) map to Asana Portfolios. Portfolios aggregate multiple projects and provide cross-project progress tracking. We enumerate the portfolio structure during discovery and recreate it in Asana with the same project membership. Portfolio creation is done post-import after all projects have been migrated.

Agilean subtasks nested within tasks migrate as Asana Subtasks. We preserve nesting depth up to the level supported by Asana (typically two to three levels of subtask nesting). If Agilean has subtasks nested beyond Asana's display depth, we migrate the deepest-level task as a top-level task under the same parent and note the structural flattening in the reconciliation report.