CRM migration
Field-level mapping, validation, and rollback between Synergy Matters and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Synergy Matters
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
10 of 11
objects map 1:1 between Synergy Matters and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
Synergy Matters is a legal-practice management platform built on MySQL — it stores contacts, companies, matters (deals), documents, disbursements, time entries, and task records with structured metadata per client. Dynamics 365 Sales runs on Microsoft Dataverse and models the same entities as Accounts, Contacts, Opportunities, Notes, and Tasks, plus custom tables for legal-matter attributes. FlitStack AI extracts from Synergy Matters via its MySQL backend and the exposed API surface, then maps each table to Dataverse equivalents. We carry contact names, company affiliations, matter identifiers, disbursement amounts, and time-tracking entries. Document files are re-uploaded to Dynamics 365 SharePoint/OneDrive integration. We surface matters and custom fields as Dataverse custom tables, so your Dynamics admin can build Power Automate workflows on top of the migrated structure. For each matter, we transform the MySQL row into an Opportunity record, linking disbursement and time-entry data to custom Dataverse tables. Workflows, templates, billing configurations, and OCR settings from Synergy Matters have no Dynamics 365 equivalent — those are documented for manual rebuild.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Synergy Matters platform overview
Scorecard, SWOT, gotchas, and pricing for Synergy Matters.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Synergy Matters object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Synergy Matters
Client / Contact
Microsoft Dynamics 365 Sales
Contact
1:1Synergy Matters stores client contacts in the contacts table with name, email, phone, and company affiliation. FlitStack AI maps each contact to a Dataverse Contact record, resolving the primary company affiliation to a Dynamics 365 Account via AccountId lookup. Multi-company contacts (if stored N:N) collapse to one primary AccountId; additional affiliations surface in Account Contact Relationships.
Synergy Matters
Client Record
Microsoft Dynamics 365 Sales
Account
1:1Synergy Matters client records map directly to Dynamics 365 Account entries. The client name, address, and industry metadata migrate as Account.Name, Address fields, and Industry pick-list values. Parent-child client hierarchies (if represented as matter hierarchies) map to Account.ParentAccountId for nested structures.
Synergy Matters
Matter / Matter Record
Microsoft Dynamics 365 Sales
Opportunity
1:1Synergy Matters matters are legal-matter records that map conceptually to Dynamics 365 Sales Opportunities. Each matter becomes an Opportunity with the matter name as Opportunity.Name, matter type as a custom field, and relevant financial data (billing estimate, fees accrued) mapped to Amount fields. Matter status values map to Opportunity StageName via a value-mapping table built during discovery.
Synergy Matters
Disbursement Entry
Microsoft Dynamics 365 Sales
Custom Table: Matter_Disbursement__c
1:1Synergy Matters tracks disbursements (copying costs, filing fees, courier charges) as structured financial line items. Dynamics 365 Sales has no native disbursement model. FlitStack creates a custom Dataverse table (Matter_Disbursement__c) with a lookup to the parent Opportunity and fields for Disbursement_Type__c, Amount__c, Date__c, and Billed__c.
Synergy Matters
Time Entry
Microsoft Dynamics 365 Sales
Custom Table: Matter_TimeEntry__c
1:1Synergy Matters records billable and non-billable time entries against matters. Dynamics 365 Sales has no native time-tracking entity. We create Matter_TimeEntry__c with fields for Hours__c, Rate__c, Attorney__c (lookup to Contact), Date__c, and Billable__c. The total billable value can roll up to the parent Opportunity Amount via a calculated field.
Synergy Matters
Document / File Attachment
Microsoft Dynamics 365 Sales
SharePoint / OneDrive Document Location
1:1Synergy Matters stores documents in a Windows file store per matter. FlitStack AI re-uploads the document files to the Dynamics 365 SharePoint/OneDrive integration associated with the parent Account and Opportunity. File metadata (filename, created date, author) is preserved in the SharePoint document library and linked via a Document Location record in Dataverse.
Synergy Matters
Task / Note Log
Microsoft Dynamics 365 Sales
Task / Note
1:1Synergy Matters logs tasks, notes, and scan events with timestamps and assigned staff. These map to Dataverse Task records (for action items) and Note records (for narrative entries). Original created-on timestamps and owner assignments are preserved via CreatedOn__c custom fields and OwnerId resolution by email match to Microsoft 365 user accounts.
Synergy Matters
Custom Matter Properties (MySQL columns)
Microsoft Dynamics 365 Sales
Custom Columns on Opportunity / Custom Table
1:1Synergy Matters stores matter-specific metadata as MySQL columns that are not part of the standard schema. FlitStack AI inventories every non-null custom column during discovery, creates the corresponding Dataverse custom columns (prefixed with new_), maps data types (TEXT→String, DECIMAL→Decimal, DATE→DateTime), and migrates values. Custom columns are documented in the pre-migration schema plan.
Synergy Matters
User / Employee Record
Microsoft Dynamics 365 Sales
SystemUser (owner resolution)
1:1Synergy Matters staff records (user IDs, email addresses, roles) are mapped to Dynamics 365 Sales users by email. Exact email matches resolve automatically. Records with no matching Dynamics user are flagged pre-migration so your admin can either invite the user to Azure AD or assign to a fallback owner. Active/inactive status is mapped to the IsDisabled flag on the SystemUser record.
Synergy Matters
Matter Hierarchy (Parent / Child Matters)
Microsoft Dynamics 365 Sales
Custom Table: Matter_Junction__c
many:1Some Synergy Matters setups use parent-child matter structures for related matters. Dynamics 365 Sales Opportunities do not support native hierarchical nesting. FlitStack creates a Matter_Junction__c custom table that links related Opportunities via Source_Opportunity__c and Related_Opportunity__c lookup fields, preserving the relationship without modifying the standard Opportunities table.
Synergy Matters
Billing Configuration / Fee Schedule
Microsoft Dynamics 365 Sales
Custom Field(s) on Opportunity
1:1Synergy Matters stores fee schedules and billing rules per matter type. Dynamics 365 Sales has no native billing configuration. We preserve fee schedule values as text-based custom fields (Fee_Schedule_JSON__c or discrete fields) for reference. Actual billing logic must be configured in Dynamics 365 Business Central or a legal billing add-in post-migration.
| Synergy Matters | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Client / Contact | Contact1:1 | Fully supported | |
| Client Record | Account1:1 | Fully supported | |
| Matter / Matter Record | Opportunity1:1 | Fully supported | |
| Disbursement Entry | Custom Table: Matter_Disbursement__c1:1 | Fully supported | |
| Time Entry | Custom Table: Matter_TimeEntry__c1:1 | Fully supported | |
| Document / File Attachment | SharePoint / OneDrive Document Location1:1 | Fully supported | |
| Task / Note Log | Task / Note1:1 | Fully supported | |
| Custom Matter Properties (MySQL columns) | Custom Columns on Opportunity / Custom Table1:1 | Fully supported | |
| User / Employee Record | SystemUser (owner resolution)1:1 | Fully supported | |
| Matter Hierarchy (Parent / Child Matters) | Custom Table: Matter_Junction__cmany:1 | Fully supported | |
| Billing Configuration / Fee Schedule | Custom Field(s) on Opportunity1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Synergy Matters gotchas
Documents live on a shared Windows file server, not in the database
OCR is generated locally and may not be portable as structured data
Outlook plugin email-to-matter filing is plugin-side, not server-side
On-premise minimum is Windows XP / older OS
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Discovery and MySQL schema inventory
FlitStack AI connects to the Synergy Matters MySQL database via read-only credentials and inventories all tables — standard and custom. We catalogue matter types, client relationships, disbursement tables, time-entry tables, and any non-standard MySQL columns. We also map file-store paths to matter IDs so document volumes can be estimated before migration. This phase produces a pre-migration schema report and a custom Dataverse column-definition plan that your admin (or our team) executes before data moves.
Build Dataverse custom tables and columns
Before any data loads, FlitStack delivers a step-by-step schema build plan for your Dynamics 365 Sales environment. This includes creating Matter_Disbursement__c and Matter_TimeEntry__c custom tables, adding all new_ custom columns on the Opportunity table, setting pick-list values for matter type and disbursement category, and configuring SharePoint document integration for the target Account records. Your Dynamics admin reviews and publishes the schema; we validate that all columns exist and data types match before proceeding to test migration.
Resolve owners by email match
FlitStack AI queries Synergy Matters staff records and attempts to match each one to a Dynamics 365 Sales SystemUser record by email address. Exact matches resolve automatically. Any staff record without a Dynamics user account generates a pre-migration flag report with the user's name, email, and the count of records they own. Your admin either creates Azure AD accounts and licenses them, or designates a fallback owner. No Opportunity or Contact record migrates without a confirmed OwnerId — unmatched records are held and reported separately.
Run sample migration with field-level diff
A representative slice of 50–200 records migrates first — covering contacts across multiple client accounts, opportunities with mixed matter types, disbursements, time entries, and a sample of documents. FlitStack generates a field-level diff comparing source MySQL values to Dataverse record values so you can verify that matter type mapping, disbursement linking, owner resolution, and document URL assignment are correct before the full run commits. You sign off on the diff before the production migration window opens.
Full migration with delta-pickup and audit log
The full migration run loads Accounts first (foreign-key dependency), then Contacts, then Opportunities with custom disbursement and time-entry tables linked via OpportunityId lookups. Documents are re-uploaded to SharePoint/OneDrive in parallel. A delta-pickup window (typically 24–48 hours) captures any records created or modified in Synergy Matters during the cutover. FlitStack generates a full audit log of every create and update operation, including source Synergy Matters IDs mapped to Dataverse record IDs for traceability. One-click rollback reverts all Dataverse changes if reconciliation against the Synergy Matters source reveals a discrepancy above your agreed tolerance threshold.
Platform deep dives
Synergy Matters
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Synergy Matters and Microsoft Dynamics 365 Sales .
Object compatibility
1 of 8 objects need a manual workaround.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Synergy Matters: Not applicable — no public API..
Data volume sensitivity
Synergy Matters doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Synergy Matters to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Synergy Matters to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Synergy Matters
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.