Migrate from Synergy to Trello

Synergy Projects map 1:1 to Trello Boards. The Project name becomes the Board title, Project description migrates to the Board description field, and Project creation timestamp is preserved. If Synergy Projects contain sub-Projects or Jobs that behave as sub-projects, these become separate Boards linked by a Board reference custom field we add to both. Synergy's template associations are not carried forward; we document which source template each Board originated from in the project manifest.

The Synergy Job Structure (folder layouts, naming rules, and folder-level permissions) does not map directly to any Trello object. We extract the full Job Structure as a manifest document, identify the top-level folder layer, and transform that layer into Trello Lists within each Board. Nested sub-folders are represented as child Card groups or as separate Boards linked via cross-reference fields. Permission assignments from Synergy folder-level access do not migrate; we note which Synergy roles and user groups had access to each folder for manual Trello Board member assignment post-migration.

Synergy Tasks map 1:1 to Trello Cards. Task name becomes the Card title, Task description migrates to the Card description (with HTML stripped to Trello markdown), Task status maps to the Card's List position within the Board, and Task assignees map to Card Members. Task dependencies in Synergy (predecessor/successor relationships) are not natively supported in Trello; we represent these as a linked-card custom field (dependency_card_id) and recommend a Power-Up like Dependency Dashboard or Correlations for visual dependency tracking post-migration.

Synergy Tasks that contain sub-tasks (WBS-style task breakdown) map to Trello Cards with Checklist items. The parent task becomes the Card; each child task becomes a Checklist item with its own name, assignee, and due date. This is a structural approximation: Trello does not support sub-task assignees independent of the parent card assignee, so we add the sub-task assignee as a note within the Checklist item title. Sub-tasks with due dates are represented as Checklist items with a due date annotation in the item title.

Synergy text, number, date, and dropdown custom fields map to Trello Custom Fields of the corresponding type. Multi-select dropdown maps to Trello multi-select with a note that the Standard $5 tier is required for Custom Fields. Currency fields in Synergy map to Trello number fields with a currency label appended to the field name (e.g., 'Budget (USD)') because Trello has no native currency field type. We snapshot the full Synergy custom field schema before migration to capture null fields, then populate null values with type-appropriate defaults in Trello so the schema remains complete across both platforms.

Synergy files attached to Tasks and Jobs migrate as Card Attachments in Trello. We transfer the binary content for each file using Trello's attachments endpoint. File names, descriptions, and upload timestamps migrate as attachment metadata. Version history (change records tracking who modified a file and when) does not have a Trello equivalent; we include a file version manifest document listing all version history for each file as a downloadable artifact for the customer's records. Synergy's 12d Model project files are transferred as binary attachments without any format conversion.

Synergy Task comments and issue notes migrate to Trello Card comments. The comment author maps to the Trello Card member if a matching Trello user exists; otherwise, the comment author name is preserved as text in the comment body. Comment timestamps are preserved as the comment post date. Synergy's internal change records (who created or modified a Job, Task, or File and when) do not migrate as native Trello comments; these are included in the project manifest as a supplementary data artifact.

Synergy Contacts do not have a native Trello equivalent. Trello uses Members at the Board or Card level rather than a dedicated Contact object. We handle this in two passes: first, we extract all Synergy Contacts and match them by email against Trello workspace members; matches become Board Members with their Trello role set by Synergy role (Admin maps to Trello Board Admin, Team Member maps to Board Normal). Unmatched Contacts are listed in the Contact Manifest with their role, contact info, and Synergy project associations for the customer to assign in Trello post-migration.

Synergy Teams define group-level permissions and role assignments across Projects and Jobs. Trello does not have a native Team concept at the project level; workspace membership is the only grouping mechanism. We extract the Synergy team roster for each Project and map it to Trello Board members. If a Synergy team had folder-level permissions, we flag those in the Job Structure manifest so the customer can apply Board-level member access appropriately. Synergy team role hierarchies (Project Manager, Architect, Contractor) are preserved as label color codes or a custom label field on Cards for reference.

Synergy Issue Types (e.g., Change Request, Punch List Item, RFIs, Submittals) define the category of tracking items within a Project. Trello Labels serve a similar categorization role at the Card level. We map each Synergy Issue Type to a Trello Label with a consistent color assignment. If there are more than 950 Synergy Issue Type instances across the workspace (Trello's per-board label limit), we consolidate to a smaller set of parent categories and note the breakdown in the manifest.

Synergy Associations link Jobs, Tasks, and other objects across the system to form cross-reference relationships. Trello does not have native cross-board card references. For intra-board associations (Card to Card within the same Board), we use the Card Link Power-Up or create a custom 'Related Cards' field containing the linked Card's URL. For inter-board associations (Card to Card across different Boards), we use a custom field 'Related Board' with the target Board name and Card ID. We extract the full association manifest from Synergy and rebuild it as a link map document and as inline card references where the destination Trello workspace supports the Power-Up.

Synergy's built-in project and financial reports do not migrate. The reporting engine's calculations and grouping logic are opaque and tied to Synergy-specific data structures that have no Trello equivalent. We export the underlying raw data (Project summaries, Task status, financial fields) as a CSV artifact for the customer to import into a BI tool (Google Sheets, Power BI, or Tableau) or rebuild using Trello's board analytics or a third-party reporting Power-Up. This is documented in the handoff package as a separate reporting rebuild task.