Migrate from Workzone to Asana

Workzone Workspaces are top-level organizational containers that hold all projects and team members. Asana uses an Organization as the top-level container with Projects grouped by team or portfolio. We map each Workzone Workspace to an Asana Project or a Project grouping within the Organization. Starter plan Workzone customers are limited to 3 workspaces; we count active and archived workspace usage during scoping and escalate if the Starter cap is a constraint.

Workzone Projects map directly to Asana Projects. We preserve project name, description, start date, target end date, status (active, on hold, archived), and project-level custom fields. Project permissions map to Asana's project membership model where Members have edit access and Guests have view or comment access. Archived projects in Workzone migrate as archived projects in Asana.

Workzone Tasks map to Asana Tasks within their parent Project. Standard fields migrate including title, description (rich text), assignee, due date, priority, and status. Task dependencies in Workzone (predecessor-successor relationships) map to Asana's dependency field using the Asana dependency API. Start dates migrate to Asana's start date field if the project is configured with the relevant date tracking setting.

Workzone Subtasks nest inside parent Tasks and preserve the full hierarchy in Asana. Each subtask inherits the parent project's context. Subtask assignees, due dates, and completion status migrate directly. Asana supports unlimited subtask nesting depth; Workzone supports a two-level task-subtask structure, so the mapping is straightforward with no re-hierarchy required.

Workzone Custom Fields are a paid add-on and may not exist on all plans. We first verify during scoping whether the Workzone plan includes the custom fields add-on. If present, we export field definitions (name, type, options for choice fields) and values per task. Field types map to Asana types: text to Text, number to Number, date to Date, choice lists to Enum (single-select or multi-select), and checkbox to Checkbox. Global custom fields in Asana are created at the Organization level and added to the relevant projects; local custom fields are project-specific.

Files attached to Workzone tasks and projects are downloaded from Workzone storage (250-500 GB depending on tier) and re-uploaded to Asana. We preserve attachment filenames, upload timestamps, and uploader identity. If the customer's Asana plan includes file storage limits, we flag storage requirements before migration and may recommend using Google Drive or Dropbox attachments in Asana to stay within Asana's per-user storage ceiling on lower tiers.

Time tracking in Workzone is full-featured on Team and Enterprise plans but only basic on Starter. We export logged hours, associated task, user, date, and any billable flag. Time entries map to Asana's Timesheets and Budgets add-on (available on Advanced and above) as time entries linked to tasks. If the destination Asana organization does not have the Timesheets add-on enabled, time entries are preserved as custom fields on the task (hours logged, date) and the customer enables the add-on post-migration. Starter plan time data is flagged as potentially incomplete during scoping.

Workzone expense tracking is Enterprise-only. Asana does not have a native expense tracking object. We export expense records (vendor, amount, date, category, attached receipt) and document them in a written expense inventory for the customer to import into a separate expense management tool (Expensify, Ramp, or similar) or recreate manually. This is not a standard object migration; it is a data rescue operation.

Workzone document approvals (Team-tier and above) are approval workflow records tied to specific files or project deliverables. Asana does not have a native document approval object. We export approval records including approver identity, approval status, timestamps, and comments, and deliver them as a written inventory document. The customer's admin rebuilds the approval workflow using Asana's Approvals feature (part of Asana Flow Automation) or a third-party approval tool post-migration.

Workzone task-level comments and threaded replies migrate to Asana Stories (activity feed) as comment entries. We preserve author identity (matched to Asana User by email), timestamp, and content. @-mentions in Workzone comments are preserved as plain text and mapped to Asana's @-mention syntax if the mentioned user exists in the destination Organization. Deleted Workzone users' comments are preserved with the original author name displayed.

Workzone Tags are lightweight labels applied to tasks and projects. They map directly to Asana Tags, which are Organization-level and can be applied across projects. Tag names and associations migrate 1:1. Multi-value tag arrays on Workzone tasks become multiple Asana tag assignments on the equivalent task.

Workzone Project Templates (available on Team and Enterprise, up to 5 on Starter) define reusable project scaffolding with pre-populated task hierarchies, default assignees, and due date offsets. We export the template structure as a documented template map. Asana's Project Templates (in the Organization's template library) serve the same purpose. We do not auto-create Asana templates from Workzone templates; we deliver a template mapping document and the customer creates Asana templates manually or using Asana's template duplication feature.

Workzone distinguishes between full seat users (creators, project managers) and unlimited collaborator seats (reviewers, guests, approvers). Full users map to Asana Members. Collaborators map to Asana Guests. We extract both roles separately, match by email address, and flag any Workzone users without a corresponding Asana account for the customer's admin to provision before migration begins. Inactive Workzone users are mapped to inactive Asana users to preserve assignment history without inflating seat count.

Workzone intake forms with conditional field logic auto-create projects from incoming requests. Asana does not have a native intake form-to-project creation workflow. We export the intake form field definitions, conditional logic, and project field mapping as a written intake form inventory. The customer's admin rebuilds intake workflows in Asana Forms (available on Advanced and above) or a third-party form tool (JotForm, Typeform, or similar) with Asana project creation integration.

Workzone's workload and capacity planning views give marketing managers visibility into team utilization across projects. Asana's Portfolio and Workload views provide similar visibility on Advanced and Enterprise tiers. We document the existing Workzone workload configuration (projects included, capacity thresholds, color-coded utilization rules) as a written inventory for the customer's admin to configure in Asana Portfolio or Workload views post-migration.