Migrate from Synergy to monday Work Management

Total Synergy Projects map 1:1 to monday.com Boards. The Project name becomes the Board title, creation timestamp maps to the Board creation date, and Project status maps to a monday.com Status column configured per board. We extract the full Project hierarchy (parent projects, subprojects) and model nested hierarchies as parent Items with Subitems in monday.com. Project-level custom fields (currency, date, dropdown, multi-select) map to Board-level columns of equivalent type. Synergy Project templates map to monday.com Board templates.

Synergy Tasks map directly to monday.com Items. Task name becomes Item title, assignees map via email resolution to monday.com Users, due dates map to the Date column, and priority maps to a Status or Priority column. Task dependencies (Successor/Predecessor relationships in Synergy) map to monday.com Dependency columns with row-to-row links. Task-level custom fields migrate as Item-level columns typed to match Synergy field types.

Synergy Job Structures define folder layouts, naming rules, folder-level permissions, and issue types per Project. These are deeply nested and firm-specific with no direct monday.com equivalent. We extract the Job Structure as a manifest and map folder-level tiers to monday.com Groups (one Group per Job Structure tier). Naming rules and folder-level permissions are documented for manual recreation in monday.com Board Settings. Issue types map to Status column values per Group.

Synergy custom fields (text, number, currency, date, dropdown, multi-select) map to monday.com Board Columns of equivalent type. We snapshot the complete Synergy custom field schema before migration because the API returns only non-empty custom fields, silently omitting null values. Post-snapshot, we create all destination columns (including those that would be null on every record) and populate null values with type-appropriate defaults (empty string for text, 0 for number, null for date) in monday.com so the schema is complete.

Task-level custom fields in Synergy migrate as Item-level columns in monday.com. The column type mapping follows the same schema as Project-level custom fields. We preserve the Synergy custom field display label and internal API name as column title and column ID prefix for traceability. Multi-select custom fields in Synergy map to monday.com Multi-Select column type.

Synergy files include binary content, all version history, change records (who and when), and file-level permissions. We transfer binary file content and version metadata as monday.com File Attachments on the corresponding Item or Board. The version history (who uploaded, when, what changed) is preserved in a custom Text column documenting the version log. 12d Model project files are supported as standard file transfers; no native 12d viewer integration exists in monday.com. Folder hierarchy from Synergy Job Structure maps to monday.com Groups with manual folder naming convention applied.

Synergy Contacts are stored in the platform but the public API does not expose a Contacts endpoint. We migrate contacts via the native import/export JSON bundle which auto-collects associated groups and attributes. In monday.com, contacts from Synergy are imported as Items on a dedicated Contacts Board, or as Person column values on relevant Items (Projects, Tasks). Contact groups in Synergy map to Groups on the monday.com Contacts Board. We advise customers to validate contact record counts against the source export manifest after migration.

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. We extract the Team roster (member names, roles, and permission scopes) and map these to monday.com Teams within the destination Workspace. Synergy folder-level permissions that are tied to Job Structures are documented as a written permission matrix for the customer's admin to apply manually in monday.com Board Settings and Workspace permissions.

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 cross-references to monday.com Item Relations (when available on the destination plan) or Mirror Columns referencing Items on connected boards. We document the full association graph in a relationship manifest so the customer can verify the connected Item structure post-migration.

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, so we extract them from the bundled JSON and map Attribute values to custom columns on the relevant Item records in monday.com. Attribute types (string, number, date) are mapped to equivalent monday.com column types.

Synergy Workflows define property-triggered approval chains, resource assignments, and status transitions. monday.com Automations use a recipe-based if-this-then-that model with different trigger and action types. We do not migrate Workflows as code. We deliver a written inventory of every active Synergy Workflow with its trigger conditions, action sequence, and recommended monday.com Automation equivalent (or monday workflows if the customer is on the post-April 2026 infrastructure). The customer's admin rebuilds these in monday.com's Automation Center.

Synergy custom reports produce summaries that are difficult to replicate in external systems because the underlying calculations and grouping logic are opaque. Report exports to PDF and Excel reflect the configured report state rather than raw data. We recommend exporting the raw project and financial data from Synergy separately and rebuilding reports in monday.com Dashboards rather than relying on exported report files as migration artifacts. We deliver a written inventory of existing report configurations (filters, groupings, metrics) as a handoff document for the customer's admin to recreate in monday.com.