How long does a Synergy Matters to Odoo CRM migration take?

Most Synergy Matters to Odoo CRM migrations complete in 48–72 hours for under 25,000 records. The longest phase is schema planning — identifying Synergy MySQL columns and creating matching ir.model.fields in Odoo. Firms with 100,000+ documents or complex matter-attachment hierarchies extend to 7–10 days. The Odoo pipeline stage and team configuration is the critical-path item before data moves. We provide a detailed timeline after the initial schema audit.

Will my Synergy Matters workflows and disbursement rules migrate to Odoo?

No. Synergy workflow triggers, matter-stage-change automations, and disbursement recovery rules do not have Odoo equivalents and cannot be migrated. These are practice-specific logic that lives in Synergy's MySQL procedures or configuration tables. We export your Synergy workflow definitions as documentation for your Odoo admin to rebuild using Odoo Studio or base.automation. Billable hours migrate as data (account.analytic.line entries), but invoice-generation rules require Odoo Accounting configuration post-migration.

Can I migrate Synergy Matters custom MySQL columns to Odoo CRM custom fields?

Yes. Synergy MySQL columns storing matter-level custom properties require us to create matching ir.model.fields records in Odoo before migration begins. We support Char, Text, Selection, Float, Integer, Date, and Boolean field types. We run a schema-introspection query against the Synergy MySQL database to enumerate all non-standard columns, then generate the Odoo field-creation XML. The custom fields appear on crm.lead (matters) and res.partner (clients) as standard Odoo fields after migration.

What happens to Synergy document attachments in Odoo CRM?

Synergy document files (PDFs, Word docs, scanned images) migrate as ir.attachment records in Odoo, linked to the corresponding crm.lead via res_model='crm.lead' and res_id set to the migrated matter ID. Files are stored in Odoo's filestore. For large document counts (10,000+ files), we recommend ensuring your Odoo hosting plan has adequate disk allocation before migration. Inline images and OCR-ready PDFs preserve their original mimetype.

Does the migration affect my Synergy Matters account during cutover?

No. FlitStack AI connects to Synergy using read-only MySQL credentials — your team continues working in Synergy throughout the migration. A delta-pickup window of 24–48 hours after the initial migration run captures any new clients, matters, or documents created during the cutover. At go-live, Odoo reflects Synergy's final state. No write operations touch the Synergy database during the entire process.

How does Synergy matter status map to Odoo CRM pipeline stages?

Synergy matter status values (e.g., Active, Pending, Closed) map to Odoo stage_id records in the target sales team's pipeline. During discovery, we enumerate all distinct Synergy status values and map each to an existing or newly created Odoo stage. Stage values must belong to the team_id assigned to the migrated crm.lead — if a stage exists only in a different team's pipeline, we flag it and your admin creates the stage in the correct team before migration runs.

What happens to Synergy time entries and billable hours in Odoo?

Synergy time entries migrate as account.analytic.line records linked to the migrated matter via a reference field and to the responsible user via user_id. The hours, dates, and descriptions transfer accurately. However, Synergy's disbursement recovery rules and invoice-generation logic do not migrate — Odoo Accounting app configuration by your finance team is required to turn analytic lines into customer invoices. We document the Synergy fee rules during discovery as a rebuild reference.

Synergy Matters to Odoo CRM Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Synergy Matters is a practice-management platform built around documents, disbursements, and time tracking for law firms. Odoo CRM uses crm.lead as its unified object for both leads and opportunities, with pipeline stages managed through stage_id selection fields and team-based routing via team_id. The migration carries over client records (mapped to res.partner), matter histories (mapped to crm.lead with opportunity-type records), document attachments (mapped to ir.attachment), and billable time entries (mapped to account.analytic.line). Odoo's XML-RPC API handles the data transfer — we use batch operations to stay within rate limits. Workflows, templates, and integrations in Synergy Matters do not have Odoo equivalents and must be rebuilt post-migration. We export Synergy configuration as reference documentation for your Odoo admin to rebuild workflows and automations. The delta-pickup window captures any new matters created during cutover before the go-live sync commits, ensuring zero data loss during the transition.

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

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

Odoo CRM

What's pulling them in

Teams choose Odoo CRM for its modular architecture — one base install with one-click app additions means they can adopt CRM alone and add accounting, inventory, or sales later as the business grows.
Small businesses pick Odoo because the Community edition is free and open-source, with no per-user or contact limits, allowing full evaluation before committing to a paid Enterprise tier.
The drag-and-drop Kanban pipeline and AI lead scoring are highlighted across G2 reviews as concrete features that make lead management faster and more visual than spreadsheet-based workflows.
Odoo's native integration with email, live chat, SMS, VoIP, and WhatsApp means inbound leads from multiple channels feed into a single pipeline without third-party middleware.
Companies in retail, supply chain, and construction value that Odoo's CRM module shares the same PostgreSQL database and UI as its ERP modules, eliminating data silos between sales and operations.

Object mapping

How Synergy Matters objects map to Odoo CRM

Each row shows how a Synergy Matters object lands in Odoo CRM, 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

Odoo CRM

res.partner

1:1

Fully supported

Synergy client records map to Odoo res.partner. The partner_id field on crm.lead references res.partner. Multiple matter contacts per client collapse to one primary res.partner record with additional contacts linked via child_ids. This ensures clean contact hierarchy without duplicate entries in Odoo's address book.

Synergy Matters

Matter / Case

maps to

Odoo CRM

crm.lead

1:1

Fully supported

Synergy matters map to Odoo crm.lead as opportunity-type records. We set type='opportunity' on the crm.lead and link it to the client via partner_id. Matter status values map to stage_id pick-list values per Odoo pipeline configuration. Each matter preserves its original creation timestamp and assigned attorney.

Synergy Matters

Document / Attachment

maps to

Odoo CRM

ir.attachment

1:1

Fully supported

Synergy document files (PDFs, Word docs, scanned images) migrate as ir.attachment records with res_model='crm.lead' and res_id pointing to the migrated matter. Large files may require Odoo filestore capacity planning. The original file mimetype and upload date are preserved in the Odoo attachment metadata.

Synergy Matters

Time Entry / Disbursement

maps to

Odoo CRM

account.analytic.line

1:1

Fully supported

Synergy billable hours map to account.analytic.line entries linked to the matter's crm.lead via ref and to the responsible user via product_id defaults. Fee-calculation rules do not migrate — Odoo Accounting handles invoicing separately. All hours, dates, and descriptions transfer accurately to maintain complete time tracking history.

Synergy Matters

Matter Custom Properties

maps to

Odoo CRM

ir.model.fields (Custom)

1:1

Fully supported

Synergy MySQL columns storing matter-level custom properties require Odoo custom field creation via ir.model.fields before data lands. We create Char, Selection, Float, Integer, Date, or Boolean fields matching the source data types identified during schema introspection. This prevents silent data truncation.

Synergy Matters

Staff / User

maps to

Odoo CRM

res.users

1:1

Fully supported

Synergy user accounts resolve by email match against Odoo res.users. Unmatched staff members are flagged for your admin to create before migration runs. Owner assignment on migrated crm.lead records requires valid res.users entries — this step is sequenced before matter migration.

Synergy Matters

Matter Notes / Activities

maps to

Odoo CRM

mail.message

1:1

Fully supported

Synergy matter notes and logged activities migrate as mail.message records attached to the crm.lead. Original timestamps and author references are preserved in message creation metadata. This maintains full activity history for compliance and client communication records.

Synergy Matters

Email Integration Config

maps to

Odoo CRM

fetchmail.server + mail.mail

1:1

Fully supported

Synergy email-tied matter linking has no Odoo CRM equivalent. Emails linked to matters in Synergy migrate as mail.message records; full email threading requires post-migration IMAP/SMTP configuration in Odoo. We document the email-matter relationships for manual reconfiguration by your admin.

Synergy Matters

Billing / Invoice Rules

maps to

Odoo CRM

account.move

1:1

Fully supported

Synergy disbursement recovery rules are practice-specific and cannot be auto-migrated. Billable time entries migrate to account.analytic.line; invoice generation requires Odoo Accounting app configuration by your admin. We export Synergy fee rules as documentation for your finance team to rebuild in Odoo.

Synergy Matters

Workflow Automations

maps to

Odoo CRM

ir.actions.server + base.automation

1:1

Fully supported

Synergy workflow triggers (matter-stage-change automations) have no Odoo equivalent. We export workflow definitions as documentation; Odoo Studio or base.automation recreates them post-migration. This ensures your automated processes transfer to the new system with admin oversight.

Synergy Matters	Odoo CRM	Compatibility
Client / Contact	res.partner1:1	Fully supported
Matter / Case	crm.lead1:1	Fully supported
Document / Attachment	ir.attachment1:1	Fully supported
Time Entry / Disbursement	account.analytic.line1:1	Fully supported
Matter Custom Properties	ir.model.fields (Custom)1:1	Fully supported
Staff / User	res.users1:1	Fully supported
Matter Notes / Activities	mail.message1:1	Fully supported
Email Integration Config	fetchmail.server + mail.mail1:1	Fully supported
Billing / Invoice Rules	account.move1:1	Fully supported
Workflow Automations	ir.actions.server + base.automation1:1	Fully supported

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

Odoo CRM gotchas

High

Odoo.sh version gating blocks assisted migrations from trial

High

Enterprise modules fail to install on Community after database restore

Medium

Custom module view inheritance breaks between Odoo major versions

Medium

Custom fields risk losing their application context on Community

Low

API access for Community is gated behind the Custom Plan

Synergy Matters gotchas		Odoo CRM gotchas
Severity	Issue	Severity	Issue
High	Documents live on a shared Windows file server, not in the database	High	Odoo.sh version gating blocks assisted migrations from trial
Medium	OCR is generated locally and may not be portable as structured data	High	Enterprise modules fail to install on Community after database restore
Medium	Outlook plugin email-to-matter filing is plugin-side, not server-side	Medium	Custom module view inheritance breaks between Odoo major versions
Medium	On-premise minimum is Windows XP / older OS	Medium	Custom fields risk losing their application context on Community
		Low	API access for Community is gated behind the Custom Plan

Pair-specific challenges

Synergy MySQL schema requires schema-first custom field setup in Odoo

Synergy Matters stores matter custom properties as additional MySQL columns in the matters table. Odoo cannot accept arbitrary columns — we must create matching ir.model.fields records before data loads. If the Synergy schema is unknown (e.g., direct MySQL export without documentation), we run a schema introspection query to identify all non-standard columns and generate the Odoo field-creation XML. This adds 1–2 days to the planning phase but prevents silent data truncation during migration.
Document attachment migration hits Odoo filestore limits on large file counts

Synergy Matters stores document files on a Windows file share; each file becomes an ir.attachment record in Odoo with the file stored in Odoo's filestore directory. For firms with tens of thousands of documents, the cumulative file size can exceed default Odoo filestore allocations on shared hosting plans. We flag the total attachment volume during discovery and recommend Odoo Enterprise with expanded filestore or self-hosted PostgreSQL with sufficient disk headroom before migration begins.
Odoo pipeline stage_id requires team_id scoping — mismatched stages orphan records

Odoo CRM pipeline stages (stage_id on crm.lead) are scoped to a specific sales team via team_id. If a migrated Synergy matter assigns a stage value that does not exist in the target team's pipeline, the record defaults to an unassigned or blank stage. We map Synergy matter_status values to Odoo stage_id records per team during migration planning and validate stage existence in the target Odoo database before committing the full run.
Time entries do not auto-link to invoices in Odoo without Accounting app configuration

Synergy Matters disbursement recovery ties billable hours directly to matter invoices. Odoo stores time entries in account.analytic.line but invoice generation requires the Odoo Accounting app with timesheet-product linking configured. We migrate the hours and dates accurately; however, the invoice-generation workflow must be set up by your Odoo accountant post-migration using Odoo's timesheet invoicing rules under Accounting > Configuration > Analytic Accounts.

Migration approach

Six steps for a successful Synergy Matters to Odoo CRM data migration

Audit Synergy MySQL schema and export data via direct database query

We connect to the Synergy MySQL database using read-only credentials and run a schema-introspection query to enumerate all tables, columns, and foreign-key relationships. This identifies standard Synergy tables (clients, matters, documents, time_entries) and any custom columns added by the firm. We generate an export package as CSV/JSON with UTF-8 encoding, preserving original timestamps and relationship IDs for foreign-key reconstruction in Odoo.
Create Odoo custom fields and pipeline stages before data migration

Before any data moves, we create the ir.model.fields records corresponding to Synergy custom columns in Odoo's crm.lead and res.partner models. We also configure the pipeline stages and assign them to the appropriate team_id so stage_id values are valid on every migrated record. This schema setup is delivered as an Odoo XML data file for your admin to review and apply.
Migrate res.partner records first, then crm.lead with partner_id resolution

Odoo requires res.partner to exist before crm.lead can reference it via partner_id. We sequence the migration so all client records load first, establishing partner_id foreign keys for each matter. Then matter records load with resolved partner_id references. Mail messages and ir.attachment records load last, referencing the now-populated crm.lead IDs. This strict ordering prevents orphaned foreign-key errors during XML-RPC API operations.
Run sample migration of 100–200 records with field-level diff

A representative slice — clients, matters, documents, and time entries — migrates first against a staging Odoo database. We generate a field-level comparison report showing source Synergy values against the migrated Odoo crm.lead and res.partner fields. You verify stage_id mapping, custom field population, and attachment visibility before the full run commits. This catches any value-mapping gaps or custom field type mismatches early.
Execute full migration with delta-pickup window and audit log

The full dataset migrates via Odoo XML-RPC batch operations staying within API rate limits. A delta-pickup window of 24–48 hours captures any new Synergy matters created during the cutover. Every operation is logged to an audit table in Odoo for traceability. One-click rollback reverts the entire migration if reconciliation fails. After validation, your team goes live on Odoo CRM with full data integrity.

Platform deep dives

Context on both ends of the pair

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.

Odoo CRM

Destination

Strengths

Modular open-source architecture lets teams start with CRM and add ERP apps as needs grow, all sharing one PostgreSQL database.
Free Community edition with no contact limits and full source code access means zero licensing cost for evaluation and small deployments.
Drag-and-drop Kanban pipeline with AI lead scoring gives a visual, prioritized view of the sales funnel without requiring custom configuration.
Native integrations with email, live chat, SMS, VoIP, WhatsApp, and social media feed all inbound leads into a single unified inbox.
Active Odoo Community Association (OCA) maintains dozens of community-maintained modules on GitHub for extended functionality.

Weaknesses

Gmail and email integration reliability is a recurring complaint — threads drop and conversations scatter across inboxes, disrupting sales team workflows.
Enterprise edition pricing stacks quickly: multiple apps at per-user rates ($25–$50/user/month) plus Odoo.sh hosting costs more than many SMBs anticipate.
Setup and configuration complexity increases significantly once custom fields, automation rules, and multiple installed modules are in play.
Odoo.sh trial databases run on a version (e.g., 18.3) that is not directly migratable to Odoo.sh, blocking the assisted migration path Odoo advertises.
Version upgrades between major Odoo releases (e.g., 17→18) frequently break custom module view definitions and XPath expressions, requiring manual remediation.

	Synergy Matters Source	Odoo CRM Destination
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.	Modular open-source architecture lets teams start with CRM and add ERP apps as needs grow, all sharing one PostgreSQL database. Free Community edition with no contact limits and full source code access means zero licensing cost for evaluation and small deployments. Drag-and-drop Kanban pipeline with AI lead scoring gives a visual, prioritized view of the sales funnel without requiring custom configuration. Native integrations with email, live chat, SMS, VoIP, WhatsApp, and social media feed all inbound leads into a single unified inbox. Active Odoo Community Association (OCA) maintains dozens of community-maintained modules on GitHub for extended functionality.
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.	Gmail and email integration reliability is a recurring complaint — threads drop and conversations scatter across inboxes, disrupting sales team workflows. Enterprise edition pricing stacks quickly: multiple apps at per-user rates ($25–$50/user/month) plus Odoo.sh hosting costs more than many SMBs anticipate. Setup and configuration complexity increases significantly once custom fields, automation rules, and multiple installed modules are in play. Odoo.sh trial databases run on a version (e.g., 18.3) that is not directly migratable to Odoo.sh, blocking the assisted migration path Odoo advertises. Version upgrades between major Odoo releases (e.g., 17→18) frequently break custom module view definitions and XPath expressions, requiring manual remediation.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Synergy Matters to Odoo CRM

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Synergy Matters

Odoo CRM

How Synergy Matters objects map to Odoo CRM

What specifically takes care here

Six steps for a successful Synergy Matters to Odoo CRM data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Synergy Matters to Odoo CRM migration cost

What are you migrating?

Frequently asked questions about Synergy Matters to Odoo CRM data migrations

Can't find your answer?

Related migrations to explore

Move from Synergy Matters.
Land in Odoo CRM, intact.

Migrate from Synergy Matters to Odoo CRM

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Synergy Matters

Odoo CRM

How Synergy Matters objects map to Odoo CRM

What specifically takes care here

Six steps for a successful Synergy Matters to Odoo CRM data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Synergy Matters to Odoo CRM migration cost

Frequently asked questions about Synergy Matters to Odoo CRM data migrations

Can't find your answer?

How long does a Synergy Matters to Odoo CRM migration take?

Will my Synergy Matters workflows and disbursement rules migrate to Odoo?

What happens to my Synergy client records in Odoo CRM?

Can I migrate Synergy Matters custom MySQL columns to Odoo CRM custom fields?

What happens to Synergy document attachments in Odoo CRM?

Does the migration affect my Synergy Matters account during cutover?

How does Synergy matter status map to Odoo CRM pipeline stages?

What happens to Synergy time entries and billable hours in Odoo?

Related migrations to explore

Move from Synergy Matters. Land in Odoo CRM, intact.

Move from Synergy Matters.
Land in Odoo CRM, intact.