Migrate from Synergy to Asana

Synergy Projects map directly to Asana Projects. Project name, description, status, start/end dates, and creation timestamps migrate 1:1. We use Asana's Projects API to create each project, then populate custom fields by referencing workspace-global custom field GIDs. Template associations from Synergy are documented as a Project Template inventory for the customer's admin to reapply in Asana via the Duplicate Project feature.

Synergy Tasks map to Asana Tasks within the corresponding Project. Task name, description (rich text), assignee, due date, start date, status, and custom fields migrate 1:1. Subtask hierarchy migrates as Asana Subtasks (nested tasks) preserving the full depth. Dependencies between Tasks migrate as Asana dependencies using the Task Dependencies API. We resolve assignee email addresses to Asana User GIDs at migration time.

Synergy Task comments migrate to Asana Stories. Story text content, author (by email lookup), and timestamp preserve. Asana Stories also capture task creation and status-change events, which we supplement with entries captured from the Synergy change log.

Synergy Contacts do not have a public API endpoint. We extract Contacts via the native import/export JSON bundle which auto-collects associated groups and attributes. Each Contact email maps to an Asana User (for assignees and project members) or to a Contact stored as a custom field reference if the customer needs contact records without user accounts. We reconcile contact counts against the export manifest to detect any silently dropped records.

Synergy Teams define group-level permissions and role assignments for Projects and Jobs. They migrate to Asana Teams as the organizational unit. Team name, member list, and team-level project visibility migrate 1:1. Role assignments from Synergy that have no direct Asana equivalent (e.g., firm-specific job roles) are documented as a role matrix for the customer's admin to map to Asana project-level permissions post-migration.

Synergy custom fields (text, number, currency, date, dropdown, multi-select) map to Asana custom fields. We snapshot the complete custom field schema including null fields before migration because Synergy's API omits null custom fields from output. We recreate null fields in Asana with type-appropriate default values so the schema remains complete. Multi-select in Synergy maps to Asana enum custom fields with multiple enum values enabled. Dropdown maps to a single-value enum. Currency maps to a number field with a display unit label.

Synergy Job Structure includes folder layouts, naming rules, folder-level permissions, issue types, and dashboard configurations deeply nested and tightly coupled to individual firm setups. Asana has no equivalent folder-permission model. We extract the full Job Structure as a structured manifest, map folder hierarchy to Asana Sections within Projects, document naming patterns as a template reference for the customer to reapply, and flag unsupported permission models for manual review before go-live.

Synergy Files transfer with content, version history, and change metadata (who and when). Asana Attachments are associated with tasks or projects. We migrate the most recent file version as the primary attachment. Historical versions are documented as a file version manifest. Note: Asana's API does not support attachments larger than 100 MB. Files exceeding this are flagged and delivered as a separate download package with links in Asana task descriptions. 12d Model project files are handled as standard attachments with no native version diff.

Synergy file version history (who modified a file and when) has no direct Asana equivalent. We extract the version change log as a structured JSON manifest and attach it as a task description block or custom field reference on the task to which the file is linked, preserving audit trail without native version tracking in Asana.

Synergy Attributes store metadata values tied to Jobs, Tasks, and Files. They are collected automatically by the import/export tool as part of the job and folder metadata package. We map Attributes to Asana custom fields scoped to the relevant task or project, inferring the appropriate field type from the attribute value format. Attributes with no mappable custom field are preserved in a structured JSON field for manual review.

Synergy Associations link Jobs, Tasks, and other objects to form cross-reference relationships. Asana natively supports Task Dependencies (finish-to-start, start-to-start, finish-to-finish, start-to-finish) and project membership linking tasks to projects. We map cross-object associations to the closest Asana equivalent: task-to-task associations become dependencies; task-to-project associations become project membership. Associations with no Asana equivalent are preserved in a custom field reference.

Synergy's native financial sync with QuickBooks Online, Xero, MYOB, and Dynamics 365 Business Central does not have a direct Asana equivalent. Financial data (AP/AR, project profitability, billing records) remains in the source accounting platform. We document the financial sync configuration as a separate integration plan for the customer's admin to reconnect under a new accounting tool or maintain as a standalone system. This object is not migrated but is inventoried and handed off.