Migrate your Workamajig data

Projects are the core Workamajig object with a stable schema, custom fields, task hierarchies, and billing associations. We export via the projects module (20 req/min rate limit) in staggered batches and preserve all linked metadata including dates, owners, and project-level custom fields.

Campaigns group multiple Projects for aggregated reporting, budgeting, and billing. We map the campaign-to-project linkage table and preserve campaign-level estimates, budgets, and billing records. The relationship is preserved as a parent-child mapping in the destination system.

Tasks are nested under Projects with predecessors, date ranges, hourly allocations, and completion statuses. We export the full task tree including hierarchy and cross-project dependencies, flagging any predecessor links that reference tasks outside the exported scope.

Deliverables represent reviewable outputs tied to approval workflows. We export deliverable records with their approval statuses, reviewer assignments, and linked project associations. Custom deliverable field schemas require field-level mapping against the destination system's equivalent object.

Workamajig supports custom fields on Projects, Campaigns, Companies, Contacts, Employees, and Order lines. We extract the full custom field schema (field types, required flags, choice options) and map each field to its destination equivalent. Renaming or restructuring custom fields post-migration is common and we handle this explicitly in scoping.

The CRM module includes Companies and Contacts with their own custom field sets. We export both objects with their relationship links, contact roles per company, and all associated custom property values.

Time entries are linked to Projects, Tasks, and Employees with billable/non-billable flags and hourly rates. We export the full time-entry history including dates, duration, billable amounts, and ownership to preserve utilization and billing data.

Workamajig generates client invoices from Projects, Campaigns, or direct billing worksheets. Invoice line items, payment status, and linked transaction records require value mapping since billing structures differ significantly between source and destination systems.

Purchase orders track vendor expenses against Projects. We export PO headers, line items, and vendor associations, but fiscal or expense-account mappings to the destination ERP require explicit field-level mapping work.

Activities capture engagement history on Companies and Contacts. The activities module is read-only via API (GET only) at 50 req/min. We export available activity records, but automation rules or activity sequences tied to workflows may not carry over 1:1.

Workamajig's custom reports and datasets are exportable to CSV, Excel, PDF, or Google Sheets. Report definitions themselves (column layouts, filters, groupings) are not easily transferable; we export the underlying data the reports surface rather than the report configurations.

Media items (Print, Broadcast) are used to categorize ad-buy purchases and map them to expense accounts in the GL. These are internal accounting categorization objects with no meaningful equivalent in standard PM destination systems, so we do not migrate them.