Migrate from Gauss Box Projects to Asana

Gauss Box Projects map directly to Asana Projects. We preserve the project name, description, start date, end date, status, and budget fields. Project-level permissions migrate as Asana organization membership and project-level privacy settings. If Gauss Box project has a status field (active, archived), we map to Asana's project archived status.

Gauss Box Phases map to Asana Sections within each Project. The sequential ordering of phases is preserved by setting Section order to match the original phase sequence. Phase-level start and end dates are noted as Section-level metadata in Asana's custom fields. Asana does not have native Phase objects, so Section is the closest structural equivalent for grouping tasks into sequential stages.

Gauss Box Tasks map to Asana Tasks with name, description, start date, due date, assignee, and priority preserved. Task status from Gauss Box (active, completed, on-hold) maps to Asana completion status. We resolve assignee by matching Gauss Box user email to Asana workspace member and set the Task assignee accordingly. Tasks without a matching Asana user are flagged in the reconciliation report.

Gauss Box Subtasks map to Asana Subtasks. Parent-child relationships are preserved by resolving the parent Task GID after initial task import. Subtask order within a parent task is preserved. We batch parent resolution to avoid sequential dependency issues during import and re-run parent lookups for any subtasks where the parent task GID was not yet confirmed during the initial pass.

Gauss Box Gantt chart data (start dates, end dates, task dependencies, phase timelines) maps to Asana Timeline view. This requires an Asana Premium or higher tier because Timeline is not available on Basic. If the customer is on Asana Basic, we map start/due dates to the task calendar view and flag Timeline as a tier upgrade recommendation. Dependencies between tasks migrate as Asana dependency links (predecessor-successor relationships).

Gauss Box Kanban board columns and card positions map to Asana Boards view. Column names migrate as Column headers, and card order within each column is preserved. If Gauss Box uses additional columns beyond To Do, In Progress, Done, we create matching Board columns in Asana. We note that Asana's Board view is available on Premium+.

Gauss Box time entries (hours logged, time estimate, actual time, user who logged) map to Asana custom fields on Tasks. Asana's native time tracking is only available on Premium+ and stores time per task rather than as standalone time entry records. We create a custom field set in Asana to hold the original Gauss Box time data: Time Estimated (hours), Time Logged (hours), Time Remaining (calculated). If the customer upgrades to Asana Premium, we can map to native time tracking.

Gauss Box task and project comments map to Asana Comments on the corresponding Tasks. Comment body, author (resolved by email to Asana user), and timestamp migrate directly. If the comment references an attachment, we ensure the attachment migration precedes the comment import to preserve inline references.

Gauss Box file attachments on Tasks and Projects migrate to Asana Attachments. We download files from Gauss Box (coordinating with their team for bulk export if needed), then upload to Asana using the attachment endpoint. File name, file type, and uploader are preserved. Storage tier constraints from Gauss Box are flagged during scoping; we confirm whether the customer needs to upgrade Gauss Box storage before export or whether all files can be extracted within the current tier.

Gauss Box Custom Fields via attribute sets are user-defined with no fixed schema, so we inventory the full attribute set during discovery before mapping. Field names, types (text, number, date, dropdown), and values migrate to Asana Custom Fields with matching types. Single-select Gauss Box attributes map to Asana enumerations; multi-select map to multi-enum. We note that Asana enforces custom field name uniqueness per workspace, so duplicate attribute names from Gauss Box require disambiguation during import.

Gauss Box Users map to Asana workspace Members. User name, email, department, and role migrate directly. External collaborators in Gauss Box map to Asana Guest members, which have restricted permissions (can only access invited projects). We flag any Gauss Box external collaborators who may need elevated Asana permissions beyond Guest level before migration.

Gauss Box Departments map to Asana Teams. Department hierarchy is not directly represented in Asana Teams, so we create Teams that correspond to departments and map users to their respective Teams. If the customer requires org-chart visibility, we recommend Asana's Portfolio or a separate organizational mapping maintained in custom fields.

Gauss Box custom project roles and permission levels are mapped to Asana project-level permissions (Can Edit, Can View, Full Access). Gauss Box's employee, client, and external collaborator role types map to Asana Member, Guest, and limited-access Guest respectively. We document the permission mapping in the migration handoff and note that Asana's permission model is project-scoped rather than globally role-based.

Gauss Box Dashboard widgets (project health, team activity, resource usage) do not have a direct Asana equivalent. Asana's Portfolio view provides cross-project status and progress visualization. We map Gauss Box dashboard widget configurations to a written description for the customer to recreate as Asana Portfolios and custom dashboards. The underlying data (task completion rates, time logged, project deadlines) migrates as task and project fields that can be surfaced in the Portfolio.