Migrate from Workzone to Microsoft Project

Workzone Workspaces map to Microsoft Project files. Starter-tier customers limited to 3 workspaces may need to consolidate before migration; Team and Enterprise have unlimited workspaces. We export each Workspace as a separate Project file (MPP format) or create a separate Project for the web plan per Workspace. Workspace-level permissions map to Project sharing settings or SharePoint site permissions depending on the destination architecture.

Workzone Projects map to the top-level summary task in a Microsoft Project file, with project metadata (name, description, status, dates, client) preserved in the Project Summary fields. Project-level custom fields map to Microsoft Project custom fields (Text1-30, Number1-10) if the customer's plan includes the custom fields add-on. If custom fields are absent, we document the gap in the field map delivered before migration begins.

Workzone Tasks map to Microsoft Project Tasks with standard fields preserved: Task Name, Start Date, Finish Date, Duration, Priority, Status, and Description (mapped to Notes in Project). Workzone's Priority values (High, Medium, Low) map to Microsoft Project Priority field (1-10 scale or custom). Task assignments map to Resource Assignments in Project with the caveat that Workzone assignees must match an existing Resource in the destination Project file exactly.

Workzone Subtasks map to Microsoft Project child tasks at the correct outline level. We preserve the parent-child hierarchy by exporting the Workzone task indent structure and reconstructing it in Microsoft Project using outline level numbering. Subtask assignees, due dates, and status inherit from the parent task in Workzone but are independent in Microsoft Project; we ensure all subtask-level values are explicitly set on the child task rather than relying on inheritance.

Workzone task dependencies map to Microsoft Project predecessor links. The Workzone knowledge base confirms that only finish-to-start dependency types import correctly from Microsoft Project; other dependency types are converted and may cause scheduling errors. We audit Workzone dependencies for any non-FS type and convert them to finish-to-start during the transform phase, flagging the change in the mapping document delivered to the customer. Cross-project dependencies in Workzone cannot be modeled in a single Microsoft Project file; these map to external predecessor links or are documented as requiring manual reconstruction in Project Online if that is the destination.

Workzone custom fields (number, date, dropdown types) are a paid add-on. If present, we map them to the equivalent Microsoft Project custom field type: numeric values to Number fields, dates to Date fields, dropdown selections to Text fields with a documented picklist. Workzone's 20-custom-field maximum means the mapping is bounded. We check the plan tier during scoping and flag whether custom fields are present before mapping begins.

Files attached to Workzone tasks and projects do not migrate through the native import path. We download all attachments from Workzone during the export phase, preserving filenames and task associations in a mapping spreadsheet. The customer uploads files to SharePoint or Project Online document libraries after migration, and we update task Notes to include links to the re-uploaded files. Workzone's Team tier provides 500 GB storage; Starter provides 250 GB. We count attachment volume during the audit phase and escalate if the re-upload scope exceeds reasonable manual effort.

Time tracking is a Team and Enterprise feature in Workzone. Starter plans have only basic time tracking or no time entries. We map logged hours to Microsoft Project Task Actual Work fields, preserving the associated task and user. If Workzone time entries include billable rates or cost data, we map them to Cost fields in Microsoft Project (Cost1-10 custom fields). We audit the customer's Workzone plan tier during scoping to determine whether time entries exist and whether they are complete.

Workzone tags are lightweight labels applied to tasks and projects. Microsoft Project does not have a native tagging model. We map tags to a Text custom field (Text1) with comma-separated values, or to the Categories field if the customer uses Project for the web. Multi-value tag arrays are preserved as pipe-separated or comma-separated strings in the text field, and the customer documents the tag-to-category reconstruction plan during scoping.

Workzone task comments map to Microsoft Project Task Notes with author name and timestamp preserved as a text prefix. Threaded replies are flattened into a single Notes field with reply separators. @-mentions and collaborator references are preserved as plain text since Microsoft Project does not support inline mentions. Large comment threads that exceed the Notes field character limit are summarized and the full comment history is delivered as a separate document linked from the task.

Workzone project templates on Team and Enterprise tiers migrate as separate Project files (MPP format) that the customer's PMO can use as baseline templates in Microsoft Project. Template structure including task scaffolding, default assignees, and default dates transfers to the template file. Enterprise templates with conditional intake form mappings do not transfer since Microsoft Project does not have an equivalent intake form feature; these are documented for manual reconstruction.