CRM migration

Migrate from Synergy Matters to Microsoft Dynamics 365 Sales

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 logo

Synergy Matters

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

91%

10 of 11

objects map 1:1 between Synergy Matters and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Synergy Matters logo

Synergy Matters

What's pushing teams away

  • On-premise architecture (MySQL plus shared file server, minimum Windows XP) is increasingly out of step with the cloud-first practice-management market dominated by Clio, MyCase, and PracticePanther.
  • Sales-led pricing with no public tier sheet makes budget comparison against transparently-priced cloud competitors awkward.
  • Limited public review footprint — G2/Capterra coverage is thin, so prospective buyers cannot easily benchmark against alternatives.
  • No documented public API or developer portal — integrations rely on Outlook/Word plugins and one-shot accounting-system exports rather than a programmable surface.
  • Cloud Edition exists but it is positioned as an alternative product rather than the primary path, which complicates the upgrade story for firms that want to move off self-hosting.

Choosing

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pulling them in

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
  • Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How Synergy Matters objects map to Microsoft Dynamics 365 Sales

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

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

Synergy 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

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

Synergy 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

maps to

Microsoft Dynamics 365 Sales

Opportunity

1:1
Fully supported

Synergy 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

maps to

Microsoft Dynamics 365 Sales

Custom Table: Matter_Disbursement__c

1:1
Fully supported

Synergy 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

maps to

Microsoft Dynamics 365 Sales

Custom Table: Matter_TimeEntry__c

1:1
Fully supported

Synergy 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

maps to

Microsoft Dynamics 365 Sales

SharePoint / OneDrive Document Location

1:1
Fully supported

Synergy 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

maps to

Microsoft Dynamics 365 Sales

Task / Note

1:1
Fully supported

Synergy 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)

maps to

Microsoft Dynamics 365 Sales

Custom Columns on Opportunity / Custom Table

1:1
Fully supported

Synergy 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

maps to

Microsoft Dynamics 365 Sales

SystemUser (owner resolution)

1:1
Fully supported

Synergy 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)

maps to

Microsoft Dynamics 365 Sales

Custom Table: Matter_Junction__c

many:1
Fully supported

Some 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

maps to

Microsoft Dynamics 365 Sales

Custom Field(s) on Opportunity

1:1
Fully supported

Synergy 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.

Gotchas + challenges

What specifically takes care here

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 logo

Synergy Matters gotchas

High

Documents live on a shared Windows file server, not in the database

Medium

OCR is generated locally and may not be portable as structured data

Medium

Outlook plugin email-to-matter filing is plugin-side, not server-side

Medium

On-premise minimum is Windows XP / older OS

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Pair-specific challenges

  • Custom MySQL columns require pre-migration Dataverse schema build

    Synergy Matters stores matter-specific metadata as arbitrary MySQL columns — there is no formal custom-field registry. Dynamics 365 Sales (Dataverse) requires each custom property to be formally defined as a column before data can load. FlitStack inventories every non-standard column during discovery, generates a Dataverse column-definition plan, and your admin (or our team) must create the columns — with correct data types (TEXT→String, DECIMAL→Decimal, DATE→DateTime) — before the migration run. Failing to pre-build the schema results in columns being skipped or truncated during load.

  • Disbursements and time entries have no native Dynamics 365 Sales home

    Synergy Matters treats disbursement tracking and time logging as first-class data — they are structured records linked to matters with type, amount, date, and billing status. Dynamics 365 Sales has no built-in entity for these. FlitStack migrates them to custom Dataverse tables (Matter_Disbursement__c and Matter_TimeEntry__c) with lookup fields back to the parent Opportunity. However, Dataverse does not enforce referential integrity on custom tables the way it does on standard entities, and rollup fields on Opportunities cannot aggregate from custom tables without a plug-in or Power Automate flow — your team must configure those post-migration.

  • Document re-hosting doubles cutover time for file-heavy matters

    Synergy Matters stores documents in a Windows file-store path per matter — sometimes thousands of files per matter for litigation or transaction practices. Each file must be downloaded from the source file store and uploaded to the Dynamics 365 SharePoint/OneDrive document location. The Dataverse SharePoint integration enforces a 50 MB per-file limit (configurable to 120 MB). For practices with large document volumes, file migration can extend the cutover window by 24–48 hours beyond the standard data migration run, especially if throttling on the Microsoft Graph API applies.

  • Billing configuration and fee schedules have no Dynamics 365 equivalent

    Synergy Matters stores matter-specific billing configurations — hourly rates, fixed fees, contingency percentages, and billing templates — as structured records in MySQL. Dynamics 365 Sales has no billing-rules engine. FlitStack preserves fee-schedule data as JSON in a custom text field (new_FeeSchedule__c) for reference, but the billing logic itself must be re-implemented in Dynamics 365 Business Central or a legal-billing add-in. This is a manual-rebuild item disclosed upfront so your team can plan the Business Central configuration in parallel.

  • Inactive Synergy Matters staff may block owner resolution

    Synergy Matters deactivates staff records rather than deleting them, and some staff may have left the firm without a corresponding Azure AD account. Dynamics 365 Sales OwnerId requires a valid, active SystemUser record. FlitStack flags every Synergy Matters staff record that cannot be resolved by email match before the migration runs. Your admin must decide whether to invite the departed user to Azure AD (licensing cost applies) or reassign their records to a fallback owner. Records without a resolved owner are held in a staging queue and reported separately.

Migration approach

Six steps for a successful Synergy Matters to Microsoft Dynamics 365 Sales data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Synergy Matters logo

Synergy Matters

Source

Strengths

  • Law-firm-specific matter-centric data model with built-in matter security.
  • Automatic OCR on incoming documents producing searchable PDFs.
  • Auto-tracked print, fax, and scan disbursements with no file codes required.
  • Outlook and Word plugins file emails and documents into the matter automatically.
  • On-premise deployment satisfies firms with strict data-residency or self-hosting preferences.

Weaknesses

  • On-prem MySQL + file server architecture is dated versus cloud-first competitors.
  • Pricing not published; quote-only.
  • No public API or developer portal; integrations rely on plugins and accounting exports.
  • Limited public review and analyst footprint.
  • Documents and metadata live in two distinct stores, increasing migration complexity.
Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Destination

Strengths

  • Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
  • Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
  • AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
  • Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
  • Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

  • Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
  • October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
  • Implementation typically requires costly certified partners, adding 30–50% to total project cost
  • Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
  • Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a manual workaround.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Synergy Matters and Microsoft Dynamics 365 Sales .

  • Object compatibility

    B

    1 of 8 objects need a manual workaround.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Synergy Matters: Not applicable — no public API..

  • Data volume sensitivity

    B

    Synergy Matters doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Synergy Matters to Microsoft Dynamics 365 Sales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Synergy Matters to Microsoft Dynamics 365 Sales data migrations

Answers to the questions buyers ask most during Synergy Matters to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Synergy Matters to Dynamics 365 Sales migrations complete in 48–72 hours of clock time for environments under 25,000 records. Document-heavy practices with thousands of files per matter can extend the file-hosting phase by an additional 24–48 hours. Larger setups exceeding 100,000 records or those with complex matter hierarchies (parent/child) typically run 5–10 days. The Dataverse schema-build step (Step 2) is the longest planning task before any data moves — it runs concurrently with migration planning and does not block the discovery phase.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Synergy Matters.
Land in Microsoft Dynamics 365 Sales , intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day