Migrate from Worksection to Microsoft Project

Worksection Projects map to Microsoft Project files or Project Online/Planner plans. Project name, description, start date, target finish date, and status migrate directly. Worksection's project-level custom fields map to Microsoft Project custom fields on the project summary task or a linked project information sheet. Project-level color tags and pinned images are dropped by Worksection's own export logic — we flag these as cosmetic gaps at scoping.

Worksection Tasks map to Microsoft Project Tasks. Task name, description, start date, finish date, priority, and status transfer directly. Tasks with Subtasks become Summary Tasks in Microsoft Project; the subtasks become child rows in the WBS outline. We preserve the indentation level from Worksection's task hierarchy during import so the outline structure matches.

Worksection Subtasks map to Microsoft Project child Tasks nested under their parent Summary Task. The parent-child relationship is preserved via outline level in Microsoft Project. We resolve any Subtask assignees and due dates as task fields. Subtasks without a parent in Worksection are imported as independent tasks.

Worksection task dependencies visible in the Gantt chart transfer as Microsoft Project Predecessor links. We map the Worksection dependency type (Finish-to-Start is most common) to the Microsoft Project DependencyType field. Lag time and lead time values migrate as offset fields. Note: Worksection's 'next stage' pipeline linking is dropped by Worksection's export logic and has no equivalent in Microsoft Project's dependency model.

Worksection time entries (hours logged against a task with optional description and rate) merge into Microsoft Project Actual Work on the matching task. The time entry author is recorded in a custom field if the customer requires time-by-person attribution; otherwise the aggregated hours appear as Actual Work without individual assignment. If rate-based cost calculation is needed, we create a Resources sheet with rate values and use the Cost field on tasks.

Worksection Members and their role assignments map to Microsoft Project Resources. We extract name, email, and role from the Worksection member list and create a Resource sheet in Microsoft Project. Role-based permissions (Admin, Manager, Member, Guest) from Worksection do not have a direct Microsoft Project equivalent and are recorded in a custom field for the customer's PMO to reassign in SharePoint permissions or Planner plan access post-migration.

Worksection Labels and stage tags transfer as text values in a Microsoft Project custom field (Text1 or a named custom field). If the customer uses color-coded stages for workflow status, we replicate the stage name as a custom flag field with a mapping table provided in the migration documentation. Note: Worksection color tags themselves are dropped by the export — only the label text migrates.

Worksection task comments migrate to Microsoft Project Task Notes. Author attribution and timestamp are preserved in the note body as a formatted header. Threaded replies are collapsed into a single note with reply attribution preserved as quoted blocks. Comments on projects (not tasks) are added as notes on the project summary task.

Worksection file attachments on tasks and projects migrate as linked files. FTP-linked files and Google Drive references from Worksection are resolved to physical files during extraction and re-uploaded to the destination SharePoint site or OneDrive location. The file URL in Microsoft Project points to the SharePoint location. Files without a resolvable URL are flagged for manual re-upload.

Worksection custom fields defined per-project via Administration migrate as named custom fields in Microsoft Project. Each project's independent schema requires field-level mapping during scoping. We match Worksection field types (text, number, date, dropdown) to the nearest Microsoft Project custom field type. Custom fields not mapped during initial scoping are flagged as deferred work for the customer's PMO to resolve post-migration.

Worksection Teams and Departments map to Resource Groups in Microsoft Project. We extract the team structure from Worksection and populate the Resource Group field on each Resource. If a Worksection member belongs to multiple teams, we use the primary team as the Resource Group value and note the additional team memberships in a custom field.

Worksection's own migration documentation explicitly states that project history, audit trails, and past-state activity logs are not transferred. This is a Worksection platform restriction, not a FlitStack AI limitation. We document this gap in the scoping report and advise the customer to export any required historical records from Worksection before the migration date if they need to be preserved as static records outside the new system.