Migrate from Synergy to Jira

Synergy Projects map 1:1 to Jira Projects as the primary container. Project name, description, creation timestamp, and key settings migrate directly. Synergy's project-level custom fields (text, number, currency, date, dropdown, multi-select) map to Jira custom fields created in the destination project. We snapshot the full custom field schema before migration because Synergy's API returns only non-empty custom fields, omitting null fields entirely; without the snapshot, empty fields vanish in Jira, breaking schema completeness.

Synergy Tasks map to Jira Issues using the most appropriate Issue Type per task's content and status. Tasks with subtasks generate Jira sub-tasks. Task status, priority, assignees, due dates, dependencies, and comments migrate directly. Synergy's dependency graph (linked predecessor and successor relationships) maps to Jira Issue Links (Blocks/Blocked By) or Jira's native dependency field depending on the Jira project configuration.

Synergy Job Structure defines the folder layout, naming rules, folder-level permissions, issue types, and dashboard configurations for each Project. It is deeply nested and varies by firm setup, with no direct Jira equivalent. We extract the full structure as a manifest (folder hierarchy, naming rule logic, permission model, issue-type assignments) and rebuild it in Jira: Jira projects receive matching configuration (issue types, screens, field layouts, permissions schemes, notification schemes), and folder naming conventions are applied to Jira project or component names. Unsupported permission models are flagged in the handoff document for manual review.

Synergy supports text, number, currency, date, dropdown, and multi-select custom fields per Project and Task. Jira's custom field types must match exactly: Synergy currency maps to Jira Number Field with formatting; Synergy dropdown maps to Jira Select List (single choice); Synergy multi-select maps to Jira Select List (multiple choice). We snapshot the complete custom field schema and field-type metadata before migration, then create equivalent Jira custom fields in the destination project via the Jira API before any data loads.

Synergy Contacts are stored but have no public API endpoint; migration uses the native import/export JSON bundle which auto-collects associated groups and attributes. Jira does not have a native Contact object in Jira Software — users are Jira Users and assignees. We map Synergy Contacts to Jira Users by email, creating Jira User accounts for any contacts not already in the destination Jira instance. Contact-level metadata (company association, phone, address) migrates to a Jira project-specific custom field group if the customer requires contact records as data rather than system users.

Synergy Teams define group-level permissions and role assignments for Projects and Jobs. The native import/export tool handles Teams as part of the metadata bundle. No standalone API endpoint exists for Teams. We extract team memberships from the JSON bundle and create Jira Groups in the destination, then assign Jira project role memberships based on the team-to-role mapping extracted from the manifest.

Synergy Files include content, all versions, change records (who and when), and file-level permissions. Jira handles file attachments as Jira Attachments linked to Issues. We transfer binary content alongside version history and change metadata. Jira's attachment size limit is 75 MB per file on most plans. Large files or 12d Model project files that exceed this limit are flagged during scoping and migrated as linked external references (URL or cloud storage link) rather than inline attachments. Version history is preserved as Jira comment entries referencing the original version metadata.

Synergy Associations link Jobs, Tasks, and other objects across the system to form cross-reference relationships. The import/export tool bundles Associations into the configuration package. We map these relationships to Jira Issue Links (Blocks, Blocked By, Relates To, Duplicate, Clone) using the Association type to determine the appropriate Jira link type. Circular dependency resolution is applied to prevent infinite link loops in Jira's issue graph.

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. There is no public API endpoint for Attributes. We extract attribute key-value pairs from the JSON bundle and map them to Jira Issue custom fields, creating the custom field in Jira if it does not already exist in the destination project schema.

Synergy's QuickBooks Online add-on synchronizes AP/AR, profitability, and financial data directly with QuickBooks. Jira does not have a native accounting or financial sync capability. Financial data, invoice records, expense tracking, and budget information in Synergy do not migrate. We recommend maintaining QuickBooks as the system of record for financial data and configuring a separate QuickBooks-to-Jira integration if Jira is used for project cost tracking. We document the financial data scope during discovery so the customer can plan accordingly.