Migrate from GUIDEcx to Asana

GUIDEcx Projects map directly to Asana Projects. We export project name, status, planned end date, customer name, custom fields, and tags. Project-level attachments transfer as file links to the project description or a dedicated project note. The destination project is created first to serve as the parent container for all subsequent phase and task imports.

GUIDEcx Phases, which are reusable template structures holding tasks and assignees, map to Asana Sections within a Project. GUIDE 1.0 templates must be cloned to 2.0 via the self-serve migration tool before export; otherwise the import silently fails to associate task structures correctly. Phase attachments are a documented bug in GUIDEcx 2026 and do not carry over when phases are created via API or UI from templates—we extract phase attachment metadata separately and re-attach as project notes at the destination.

GUIDEcx Milestones map to Asana Milestones. Milestones sit above Task Groups in GUIDEcx's five-level hierarchy and are often used as project-level checkpoints or phase gates. We export milestone name, planned date, status, and status_category. Dependencies on milestones resolve to milestone-level dependencies in Asana where available, or are flagged for manual reconstruction.

GUIDEcx Task Groups are a grouping layer below Milestones and above individual Tasks. We map them to Asana Sections to preserve the visual grouping, but we note that Task Groups carry no separate duration in GUIDEcx—duration is set on individual Tasks. Section sort order migrates from the GUIDEcx task_group sort field. Asana does not support a native equivalent of the Task Group as a standalone container with its own metadata, so any task-group-level custom fields migrate to a structured note on the Section.

GUIDEcx Tasks map to Asana Subtasks (nested under a parent task that represents the phase or section context). We export task name, instructions, due date, start date, status, status_category, assignees (internal and external), tags, checklist items, subtasks, and dependencies. The GUIDEcx completed_date field has a documented bug in the 2026 release notes—we cross-reference the API export against direct API calls to fill gaps. Assignee email addresses that have no corresponding Asana workspace user are flagged in the reconciliation queue.

GUIDEcx Custom Fields V2 exist at both project level and task level. We pull field type definitions from the GUIDE 2.0 Data Dictionary (the standard task export does not include schema) and map them to equivalent Asana field types. Dropdown options in GUIDEcx map to Asana enum values. Multi-select dropdown maps to multi-enum. Some GUIDEcx field types (such as complex validation rules or third-party system IDs) may not have a direct Asana equivalent and are flagged during scoping.

Finish-to-start dependencies from GUIDEcx map to Asana task dependencies. We preserve the dependency graph but flag known GUIDEcx 2.0 bugs: subtask-child shared dependencies and N/A-marked tasks that break dependency chains in the export. These are handled as individual records in the reconciliation queue post-migration. Asana does not cascade date changes automatically when upstream tasks complete, which is a functional difference from GUIDEcx's dependency engine.

GUIDEcx Tags map directly to Asana Labels. Tag names and task-to-tag associations migrate. Note that GUIDEcx tag colors do not map to Asana label colors because the two platforms use different color metadata. Asana labels have a 100-label per workspace limit on some plans, which we check during scoping.

GUIDEcx distinguishes between internal team members and external customer contacts. Customer Roles must be created in Resource Management before they can be assigned to a project in GUIDEcx. Asana has no native Customer Role concept. We export customer roles and contact names as structured text in the Asana project description or a project-level note, and flag the gap for the customer's admin to configure Asana Guest user access or a third-party client portal post-migration.

GUIDEcx checklist items on task templates do not reliably migrate to project-level tasks per the 2026 release notes. We treat checklists as a structured list and load them as Asana Subtasks under the parent task. Each checklist item becomes a subtask with the item name as the title and a note containing the original item description. We validate checklist completeness against the original GUIDEcx export during reconciliation.

GUIDEcx attachments at the project level and phase level migrate to Asana project attachments. Asana's API does not support attachments exceeding 100MB—we skip files above this limit and document them in the reconciliation report for manual re-upload. Phase-level attachments are a documented GUIDEcx bug when phases are created via API or UI from templates; we extract the metadata separately and re-attach as project-level links or notes in Asana.

GUIDEcx supports time tracking. The GUIDE 2.0 Time Records dataset is documented as missing values for several columns per the 2026 release notes. We export available time record fields and represent them as structured notes on the relevant task or as a custom time-tracking note field in Asana. Note that Asana's native time tracking requires an Enterprise license or a third-party integration.

GUIDEcx task comments are not included in the standard task export. We retrieve comment threads via the GUIDEcx API and represent them as structured notes attached to the corresponding Asana task, with the comment author, timestamp, and body preserved. Embedded media in comments migrates as file links where possible.

GUIDEcx Report Builder datasets (Projects, Tasks, Custom Field Details, Time Records) have documented data quality issues in the 2026 release notes and do not export as a standalone artifact. We export the available dataset data and deliver a written inventory of each report's structure, filters, and column configuration. The customer's admin rebuilds these as Asana custom views, portfolios, or workload dashboards post-migration.