Migrate from Workamajig to Asana

Workamajig Campaigns aggregate multiple Projects for budget rollup, P&L reporting, and billing across an entire client engagement. Asana has no native Campaign object. We map each Campaign to an Asana Portfolio (Business+ tier) or, if the customer is on Advanced or lower, to a top-level Project with a 'Campaign' tag and all child Projects added as sub-projects. Campaign-level budget and estimate figures migrate as Custom Fields on the Portfolio or top-level Project because Asana does not have a native budget object. The campaign-to-project linkage table is preserved via Portfolio membership or a custom Project field linking to the parent Campaign record.

Workamajig Projects map directly to Asana Projects. Each Project's name, description, status, start and due dates, and estimated hours migrate as native Asana fields. Custom fields on the Workamajig Project (client name, project type, billing tier) translate to Asana Custom Fields of matching type (text, date, number, multi-select). Workamajig's 20 req/min API ceiling on Projects requires batched export in groups of 20 with backoff delays; we paginate through all project pages before moving to dependent objects to avoid mid-migration rate-limit failures.

Workamajig Tasks map to Asana Tasks with assignees, due dates, priority flags, and task descriptions preserved. Task hierarchy under Projects migrates as Asana Subtasks within the corresponding Project. Predecessor dependencies in Workamajig translate to Dependency links in Asana (finish-to-start, start-to-start). Cross-project task dependencies are flagged during scoping because they require both Projects to exist in Asana before the dependency link can be created; we resolve parent project lookups before inserting cross-project dependency records.

Workamajig Deliverables represent reviewable creative outputs tied to approval workflows with reviewer assignments and approval statuses. Asana has no native deliverable approval object. We map Deliverables to Tasks with a custom field 'Deliverable Status' (options: Draft, In Review, Approved, Rejected) and a 'Reviewers' multi-select person field. The approval workflow logic itself does not migrate; we document the Workamajig deliverable workflow triggers and actions for the customer's admin to rebuild in Asana Rules if Business+ tier is selected.

Workamajig custom fields on Projects, Campaigns, and Tasks (field types include text, number, date, dropdown, checkbox, and currency) migrate to Asana Custom Fields of equivalent type. We extract the full custom field schema (field types, required flags, choice options) from Workamajig at scoping and pre-create the corresponding Asana Custom Fields before any data import. Asana formula custom fields are supported on Business+ plans; any Workamajig calculated fields that cannot be replicated as read-only formula fields in Asana are converted to text fields with the calculated value pre-populated.

Workamajig Companies (client and vendor records) map to Asana Organizations. Company name, industry, website, phone, and address fields migrate to the Organization's name and profile fields. Workamajig Company custom fields (billing tier, contract status, VAT number) migrate as Organization Custom Fields in Asana. Company-to-Contact relationships (the roles each Contact plays at a Company) are preserved by linking each migrated Contact to the corresponding Asana Organization.

Workamajig Contacts map to Asana Members within the destination Organization. Contact name, email, phone, role, and title fields migrate directly. Custom property values on Workamajig Contacts (preferred contact method, account manager, segment classification) migrate as Member Custom Fields. Workamajig's contact roles per Company are preserved via Organization membership and, if the customer uses Asana Guests for external contacts, by provisioning Guest access at migration time.

Workamajig time entries link to Projects and Tasks with billable/non-billable flags, hourly rates, dates, duration, and owner. Asana's native time tracking is only available on Business+ plans as a project-level feature with daily log entries, not as a historical record set. We migrate time entries as Asana Tasks under the corresponding Project with a custom field 'Time Entry' containing the original duration, billable flag, hourly rate, and date in text format. For customers on Asana Business+, we enable time tracking per project and log entries individually, respecting the API's time-tracking endpoints.

Workamajig invoices generated from Projects or Campaigns have no direct Asana equivalent. We do not migrate invoice records. We export invoice data to a CSV inventory (invoice number, client, amount, status, date, line items) and deliver it to the customer's admin. If the customer maintains billing in QuickBooks, NetSuite, or another ERP post-migration, we provide a value mapping guide for that system's invoice reconstruction. Invoices that have a project-level narrative or notes that need to be preserved are imported as Project descriptions or custom fields in Asana.

Workamajig purchase orders track vendor expenses against Projects with PO headers, line items, and vendor associations. Asana has no purchase order or expense tracking object. We export PO data to a CSV inventory and provide a written guide for reconstructing POs in the customer's accounting system. Project-level expense notes that need to be preserved migrate as Tasks or custom fields in Asana if the customer requires them in their project management view.

Workamajig Activities capture engagement history on Companies and Contacts (calls, emails, meetings logged by the agency). The Workamajig activities module is read-only via API (GET only) at 50 req/min. We export available activity records and link them to the corresponding migrated Asana Task or Project as Comments. Activity type (call, email, meeting) and timestamp are preserved in the comment body. The Workamajig Activities module does not export automation rules or activity-triggered workflows; these are documented for rebuild in Asana Rules if applicable.

Workamajig report data (CSV, Excel, PDF) is exportable. Report definitions, column layouts, filters, and grouping configurations are not transferable. We export all Workamajig report data as CSV files organized by report name and deliver them alongside the migration. Report layout reconstruction is documented in the handoff: we provide a field-mapping reference that lists every Workamajig report column and its corresponding Asana field or custom field so the admin can rebuild layouts in Asana Dashboards or export to a BI tool.

Workamajig Media Items categorize ad-buy purchases and map them to expense accounts in the general ledger. These are internal accounting categorization objects with no meaningful equivalent in Asana. Media Item records are not migrated; we flag them in the scoping inventory and direct the customer to their accounting system for this data.