Migrate from Workamajig to Microsoft Project

Workamajig Projects map directly to Microsoft Project Project objects. We extract Project Name, Project Number, Project Status (Active, On Hold, Completed), Start Date, Due Date, estimated hours, and all project-level custom field values. Workamajig's Project API is rate-limited at 20 req/min, so we paginate in staggered 20-record batches with backoff delays to avoid 429 errors. Projects with linked Campaign parents are flagged with a custom field for downstream campaign rollup grouping.

Workamajig Campaigns roll up multiple Projects for aggregated billing, budget tracking, and reporting. Microsoft Project has no Campaign object. We handle this in one of two ways during scoping: Option A maps each Campaign to a parent Project whose tasks represent phase-level rollup (all linked Project task summaries roll up to the parent); Option B creates a Campaign Register CSV that the customer uses to group related Project MPP or Project for the web plans in SharePoint folders or a Project Online Enterprise Resource Pool view. The choice depends on the customer's reporting cadence and whether they use Project Online cloud or Project Server Subscription Edition.

Workamajig Tasks nested under Projects map to Microsoft Project Tasks. We export the full task hierarchy including WBS sequence, predecessor links (Finish-to-Start, Start-to-Start, and lag time), date ranges, hourly allocations, percent complete, and task-level custom fields. Task dependencies expressed as cross-project links in Workamajig are flagged and resolved: Microsoft Project Online supports cross-project dependencies while Project Desktop Standard does not. We note which tasks have external predecessors before migration so the customer knows which environment type to target.

Workamajig stores task predecessors as linked records; Microsoft Project stores predecessors as Task Predecessorcessorcessorcessorcessors on each Task row with dependency type codes (FS, SS, FF, SF) and lag. We transform the predecessor chain into MS Project predecessor format during the export phase, mapping Workamajig's dependency types to standard MS Project dependency codes. Recurring task dependencies and conditional predecessors are flagged as requires-manual-review items since these do not always transfer reliably across systems.

Workamajig Employees and Team Members map to Microsoft Project Resources. We export resource name, email, role type (Work, Material, Cost), hourly rate (from Workamajig Role rates), and max units. Resources with no assigned tasks are included with zero assignments. Workamajig's generic Resources (non-user allocation pools) map to MS Project Material Resources or Cost Resources depending on how the Workamajig role was configured. Rate precision is preserved to two decimal places.

Workamajig task-to-resource assignments map to MS Project Assignments (TaskResourceAssignments). Each assignment carries the Work field (hours), Units (percentage or decimal), and Assignment Owner. For assignments with billable hours in Workamajig, we store the billable amount in an Assignment Notes field since MS Project has no native billing module. Workamajig's Anyone-to-Charge-Time flag is preserved as an assignment property.

Workamajig Time Entries (linked to Project, Task, and Employee with billable/non-billable flags and hourly rates) have no direct Microsoft Project equivalent. MS Project has no native time-tracking module. We export all Time Entries as Task-level Notes with a structured format: Date | Employee | Hours | Billable (Y/N) | Rate | Amount. For Project Online environments, we can alternatively attach time-entry CSVs as SharePoint document library files linked to the project. The billable/non-billable flag and hourly rates are preserved in the note text; the customer should evaluate whether to use a third-party time-tracking integration (Harvest, Tempo, or Project Online timesheets) post-migration.

Workamajig custom fields on Projects, Campaigns, Tasks, and other objects are extracted with full schema metadata (field type, required flag, choice options) and mapped to equivalent Microsoft Project Enterprise Custom Fields or SharePoint columns depending on the target environment (Project Online vs Project Desktop). Picklist and multi-select custom fields from Workamajig map to MS Project lookup tables. We flag any Workamajig custom field type without a direct MS Project equivalent (for example, complex multi-tiered picklists) for customer review before mapping.

Workamajig Deliverables with approval workflows, reviewer assignments, and status tracking have no native Microsoft Project object. We export Deliverable records as a CSV including Project association, deliverable name, description, due date, assigned reviewers, approval status, and approval date. The CSV is delivered alongside the project plan so the customer can rebuild deliverable tracking in a separate tool (SharePoint, Teams, or a dedicated approval system). Digital proofing file links are exported as URLs in the CSV; the files themselves are not migrated.

Workamajig Companies and their Contact associations have no native Microsoft Project object. We export Companies as a CSV (Company Name, Domain, Address, Industry) and Contacts as a separate CSV (First Name, Last Name, Email, Company, Role). For Project Online environments, these can be stored in a SharePoint list linked to the project site or used to build an enterprise Resource Pool in Project Server. For Project Desktop, we recommend a separate CRM or SharePoint-based client register maintained outside the MPP file.

Workamajig Invoices and their line items have no Microsoft Project equivalent. We export Invoice headers (Invoice Number, Client, Project/Campaign association, date, total amount, payment status) and line items (description, quantity, rate, amount, tax) as a CSV. This CSV is suitable for import into the customer's accounting system (QuickBooks, NetSuite, Dynamics 365 Business Central) post-migration. We do not migrate invoice PDFs as part of the standard scope; file migration is a separate engagement.

Workamajig Purchase Orders tracking vendor expenses against Projects have no native Microsoft Project equivalent. We export PO headers (PO Number, Vendor, Project association, date, total) and line items as a CSV. The customer should evaluate whether the destination accounting system (or a planned Microsoft Dynamics 365 Business Central integration) will handle vendor expense tracking post-migration. PO-to-Project linkage is preserved in the CSV as a reference field.