Migrate from Worksection to Asana

Worksection Projects map directly to Asana Projects with name, description, status, start date, and due date preserved. Project folder hierarchy is flattened into Asana Sections or sub-Projects depending on the customer's preference during scoping. Worksection's project color tags and pinned image states are dropped by Worksection's own export logic and cannot be reconstructed; we flag this as a cosmetic gap in the scope document.

Worksection Tasks map to Asana Tasks with title, description (migrated as rich text), assignee (resolved via email to Asana User), due date, priority, and status preserved. Task start date from Worksection maps to the Custom field Start Date in Asana if the customer requires it; Asana's native due_date field covers the due date. Completed_at timestamp migrates to a custom field completed_at__c for audit since Asana marks completion without storing a separate timestamp.

Worksection Subtasks map to Asana Subtasks under their parent Task. The parent-child relationship is preserved by setting the parent Task's GID as the subtask's parent reference. Worksection allows deeper nesting in some configurations; Asana supports subtasks up to 15 levels deep. If Worksection nesting exceeds this, we document the overflow and map the deepest records as top-level Tasks with a custom field parent_original_id__c for the customer's admin to reorganize manually.

Worksection time entries with hours and descriptions map to Asana time tracking entries on the corresponding Task. Worksection's hourly rate multiplied by hours produces a cost value; if the customer needs cost tracking in Asana, we create a custom currency field actual_cost__c on the Task and populate it during import. Worksection's built-in timer start/stop events do not have a separate representation in Asana and are not migrated as discrete records.

Worksection's per-task financial costs and per-project hourly rates have no native Asana equivalent. We create a custom currency field cost_actual__c on Tasks (if Advanced tier or above) and a custom currency field hourly_rate__c on Projects, populating them from the Worksection export. Cost reporting in Asana relies on Portfolio time-tracking summaries or a third-party integration; we document this gap and recommend the customer's admin evaluate Asana's native reporting or a timesheet app post-migration.

Worksection task comments map to Asana Stories attached to the Task. Author attribution (email resolved to Asana User), comment body, and original timestamp are preserved. Threaded discussions in Worksection are flattened into sequential Stories in Asana since Asana's comment model is not natively threaded.

File attachments on Worksection Tasks and Projects migrate as Asana Attachments. We resolve FTP-linked files and Google Drive references by downloading to a temporary location and uploading to Asana's attachment storage. Large attachments are chunked to respect API limits on both platforms. Image attachments and pinned images from Worksection are included, but pinned image states (visual marker position) are not preserved as they have no data representation in the export payload.

Worksection task Labels and stage tags map to Asana Tags. Multi-select labels in Worksection become multiple Asana Tags on the same Task. Worksection's color-coded labels lose their color mapping since Asana's tag color is assigned per tag name independently; we note the color-to-tag mapping in the scope document for the customer to re-apply manually if needed.

Worksection Member accounts (email, name, role) map to Asana Users. We resolve by email match during import. Any Worksection member without a matching Asana User is held in a reconciliation queue; the customer's admin provisions the missing Asana User before record import resumes. Inactive or archived Worksection members can be mapped to Asana Guests if the destination org allows Guest access, or omitted with a note in the scope.

Worksection Teams and Departments map to Asana Teams. We extract the team structure from Worksection's member-to-team assignments and create corresponding Asana Teams. If Worksection's team permissions layer (view, edit, admin) is used, we document the permission mapping for the customer's admin to reconfigure in Asana's Team settings post-migration.

Worksection custom fields created per-project via Administration require field-level mapping because each Worksection project can define its own schema independently. We consolidate all unique field names across the source account, map data types (text to Asana Text, number to Number, date to Date, dropdown to Single-select or Multi-select), and create either local custom fields on each Asana Project or global custom fields in the organization field library depending on the destination Asana tier. Custom fields are available from Asana Starter tier onward.

Worksection task dependencies visible in the Gantt chart migrate to Asana Dependencies linked to the Timeline view. We map finish-to-start dependencies directly to Asana's finish_to_start dependency type. Worksection's stage-to-stage 'next stage' linking does not transfer and is dropped by Worksection's own migration export; we document every instance of this pattern in the scope for manual reconstruction in Asana's Timeline. Start-to-start, finish-to-finish, and start-to-finish dependency types in Worksection map to their equivalents in Asana.

Worksection's project history, audit trails, and past-state activity logs are not transferred in any migration export. This is a Worksection platform restriction and applies regardless of migration destination. We flag this upfront during scoping so the customer understands that moving to Asana means losing the full chronological record of who did what and when within the existing Worksection account. There is no workaround for this data loss.