Migrate from Projectworks to Microsoft Project

Projectworks Projects map directly to Microsoft Project projects as the primary container. Project name, start date, finish date, status, and description transfer. Projectworks project-level custom fields map to Microsoft Project custom fields (up to 10 fields supported on import from MPP). We flag any Projectworks custom fields exceeding this limit and document them for manual post-import population.

Projectworks Tasks nested under Projects map to Microsoft Project tasks with WBS hierarchy preserved. Task name, start date, finish date, duration, percent complete, and predecessor dependencies transfer. Projectworks custom task fields map to custom fields in Microsoft Project. We extract the predecessor chain from Projectworks and reconstruct task dependencies in Microsoft Project, noting that complex cross-project dependencies may require manual validation in the destination.

Projectworks Milestones map to Microsoft Project milestones (tasks with zero duration and a milestone marker). Milestone name, due date, and completion status transfer. We flag milestones with no due date in Projectworks so the customer can set them in Microsoft Project before or after import.

Projectworks People records with their billable hourly rates and utilization settings map to Microsoft Project Resources. Resource name, email, capacity, and max units transfer. Billable rate from Projectworks maps to the Cost Rate table in Microsoft Project so that task assignments carry the correct billing rate. We flag any Projectworks People records without a named resource assignment and ask the customer to clarify whether they should import as a resource, a placeholder, or be excluded.

Projectworks Time Entries link hours to Projects, Tasks, and People. We migrate these as task assignment hours in Microsoft Project. Note that Projectworks timesheets record duration only, not start and finish times. The hours transfer as work values on the relevant task assignments, but the time-of-day clock-time data is not available in Projectworks and therefore cannot migrate. Staff who used third-party tools like Memtime alongside Projectworks for clock-time tracking will have duplicate records to reconcile; we flag this gap during discovery.

Projectworks Budgets defined at the Project level track planned versus actual revenue and costs. Microsoft Project has no native budget object. We extract budget line items as planned cost and planned revenue values and map them to custom number fields on the Project record. For Project for the web or Planner destinations, we map budget data to custom columns. The customer should validate budget totals against their Projectworks budget report during reconciliation.

Projectworks Expenses track reimbursable and non-reimbursable costs linked to Projects and People, with multi-currency support and Xero bill export capability. Microsoft Project has no expense tracking object. We extract all expense records as a structured CSV export including project association, amount, currency, category, and reimbursement status. The customer uses this export to rebuild expense tracking in a connected accounting tool (Xero, QuickBooks, or a separate expense management platform) or as a reference for project cost reconciliation in Microsoft Project custom fields.

Projectworks Invoices combine fixed-fee and hourly rate line items on a single invoice, a capability users value over competing platforms. Microsoft Project has no invoicing capability. We extract invoice headers, line items, and status as a structured export. The customer uses this export to re-issue invoices in their accounting system or to populate invoice reference data in custom fields on the Microsoft Project project record for historical record-keeping.

Projectworks Companies store client address, billing details, and custom fields linked to Projects and Contacts. Microsoft Project stores a project-level organization name but has no Company or Account object. We extract Company records and associate them with the relevant Projects by name match. The customer maps the client organization to the Project summary field or a custom field if cross-project client reporting is required in Microsoft Project.

Projectworks supports custom fields on Projects, People, Companies, Contacts, Timecodes, Budgets, Time Entries, Expenses, Invoices, and Quotes. Custom field schema varies per firm. We enumerate all custom field definitions during discovery, map them to Microsoft Project custom fields (up to 10) for Project and Task, and document any custom fields exceeding the destination limit for manual post-import handling. Custom fields on objects with no Microsoft Project equivalent (Expenses, Invoices, Companies) are extracted to the CSV exports alongside the parent record data.