Migrate from Synergy Matters to Twenty CRM

Synergy contacts map directly to Twenty People. Email becomes the unique identifier for matching and deduplication. Address, phone, job title, and create-date all carry over. Multiple Synergy contacts without email become Twenty People with no email, flagged for manual review.

Synergy companies map to Twenty Companies. Domain normalizes to Website. Industry values map to Twenty's industry select list where match exists; non-matching values become custom select values in Twenty's data model. Parent-child company hierarchies in Synergy map via Twenty's relation field.

Synergy matters become Twenty Opportunities. Matter name maps to Opportunity name. Matter status (open, pending, closed-won, closed-lost) maps to Twenty pipeline stages via value mapping. Billable amount maps to Opportunity amount. We create a custom Stage_History__c field to preserve Synergy's matter status change timestamps.

Synergy stores billable hours in a separate table with matter foreign keys. We create a Billable Hours custom object in Twenty with fields: Date, Hours, Rate, Amount, Attorney (linked to People), Matter (linked to Opportunity). On Free and Pro plans, Billable Hours may need to be stored as custom fields on the Opportunity instead due to the 10-object plan limit.

Synergy disbursements track out-of-pocket expenses per matter. We create a Disbursements custom object with fields: Date, Description, Amount, Matter (linked to Opportunity). If Twenty plan limits are reached, disbursements are stored as a JSON-formatted custom text field on the Opportunity record for audit reference.

Synergy document metadata (file name, file type, upload date, author) migrates as a Twenty Note attached to the relevant People or Opportunity record. The actual document files are re-uploaded to Twenty's file storage. File size limits apply; files exceeding 25MB are flagged for chunked upload.

Synergy's N:N contact-to-matter table is collapsed into a primary link (Person linked to Opportunity as primary contact) plus secondary relation records created via Twenty's relation import. All association roles are preserved in a custom Role__c field on the relation for audit continuity.

Synergy activity log entries (calls, emails, meetings) migrate as Twenty Notes attached to the relevant People and/or Opportunity record. Original entry timestamps are preserved as a custom datetime field for audit continuity. Synergy's activity type field maps to a custom Type__c pick-list on the Note.

Synergy users and staff members are matched to Twenty workspace members by email address. Active Synergy users receive Twenty accounts; inactive users are imported as deactivated records. Permissions are not migrated — Twenty permission groups are set to default and require post-migration configuration.

Synergy's freeform MySQL columns become Twenty custom fields with appropriate types (text, number, date, select). We normalize column names containing spaces or special characters to snake_case identifiers for Twenty's API. Custom fields are created before data migration so the import pipeline can reference them by API name.

Synergy's internal record IDs are stored as a custom text field on every object for traceability, delta-run deduplication, and rollback identification. The field is named Source_System_ID__c and populated with the full Synergy primary key so future syncs can reference the source record unambiguously.