Migrate from Synergy Matters to Salesforce Sales Cloud

Matter-to-Case object split requires schema decision upfront

Synergy Matters matters serve double duty as service records and revenue trackers. Salesforce separates these into Case (service) and Opportunity (revenue). If your firm tracks matter value or expected fees, matters need to map to both Case and Opportunity — a split that requires Salesforce record types and custom fields to handle cleanly. FlitStack AI surfaces this as a schema decision before migration begins, so your Salesforce admin can pre-create the necessary record types and custom fields rather than discovering the gap after data lands.

Billing rates and disbursement fields have no Salesforce standard equivalent

Synergy Matters stores billing rates and disbursement types per matter — these are legal-industry-specific constructs with no Salesforce standard field counterpart. We create Billing_Rate__c (currency) and Disbursement_Type__c (text) custom fields on the Case object, but your team needs to decide how these feed into any downstream billing or invoicing tool. Salesforce's native billing model is built for product-line Opportunity Products, not hourly legal matters — the custom fields preserve the data for reference or integration but do not automatically generate invoices.

Document re-hosting requires file-size and storage planning

Synergy Matters documents attached to matters are downloaded from Synergy's storage and re-uploaded to Salesforce Files. Salesforce Files have a 25MB per-file default limit and count against your org's data storage allocation. Large document repositories in Synergy Matters can generate significant Salesforce storage consumption — we flag total document volume and file-size outliers before migration so your team can plan storage accordingly or use Salesforce Content Libraries for archival purposes.

Owner resolution by email may leave orphaned assignments

Synergy Matters staff members resolve to Salesforce Users by email address match. Any Synergy Matters owner whose email does not correspond to an active Salesforce User account is flagged before migration. Records for unmatched owners land in a designated fallback owner queue — your Salesforce admin needs to either create the missing User records or manually reassign records post-migration. We do not silently drop records due to owner mismatch, but we do require your team to confirm the owner mapping before the full run commits.

Synergy Matters API export is scoped — not all metadata migrates

Synergy Matters' export API covers core records (contacts, clients, matters, time entries, documents) and custom field values. System configuration data — workflow rules, email templates, document folder structures, and billing rule definitions — are part of Synergy's application configuration and do not export via API. These items must be manually rebuilt in Salesforce or exported as documentation for your admin. We include a configuration export summary as part of the migration package so your team has a rebuild reference.