MyCase to Odoo CRM migration
Moving from MyCase to Odoo CRM translates a legal-practice management system into a modular ERP-CRM platform. FlitStack AI maps MyCase contacts, companies, cases, time entries, and billing data into Odoo res.partner and crm.lead — preserving original create dates, case numbers, and custom fields while Odoo handles the rebuild of your practice workflows in its action-rule engine.
FlitStack AI migrates res.partners, crm.leads, crm.lead.user_ids, crm.lead.stage_ids and mail.messages from MyCase to Odoo CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 10,000 records.

What moves from MyCase to Odoo CRM?
MyCase is a legal practice management platform centered on Cases, Contacts, Companies, Time Entries, and integrated billing.
Read the full summary
Odoo CRM models leads and opportunities in crm.lead, contacts and companies in res.partner, and cross-references them through partner_id and partner_email fields. The fundamental structural difference is that MyCase treats a Case (matter) as the primary entity with Contacts nested inside it; Odoo CRM treats Opportunities (crm.lead) and Contacts (res.partner) as co-equal objects joined by relational fields. This migration carries MyCase records into Odoo by creating res.partner entries for every Contact and Company, then creating crm.lead records for every Case — storing the original MyCase case number, case type, practice area, and responsible attorney as custom fields on each crm.lead. Time entries migrate as mail.message records on the relevant crm.lead so activity history is preserved. Custom fields defined in MyCase are recreated as ir.model.field definitions in Odoo before data lands. Workflows, automations, and document templates do not transfer — FlitStack exports their definitions for your Odoo administrator to rebuild using Odoo Studio or server actions. The migration runs against Odoo's xmlrpc API, respecting Odoo's per-database connection limits and PostgreSQL-backed transaction integrity.
Contact → res.partner
MyCase contacts map 1:1 to Odoo res.partner records.
How it maps
The email field is used as the unique matching key for owner resolution. Contacts without an email receive a generated placeholder email and are flagged for manual review before the full migration commits.
Company → res.partner (company_type = 'company')
MyCase companies map to Odoo res.partner with company_type set to 'company'.
How it maps
The primary address, phone, and website fields migrate directly. Parent-company relationships in MyCase map to res.partner parent_id — the parent company must be created before the child to resolve the foreign key.
Case → crm.lead
MyCase cases become Odoo crm.lead records.
How it maps
The case number (e.g., '2024-CIV-001') is stored in a custom field x_mycase_case_number on crm.lead. Case type (litigation, transactional, estate) maps to a custom selection field x_practice_area on crm.lead. The crm.lead name field is populated with the case title for Odoo pipeline visibility.
Case.assigned_attorney → crm.lead.user_id
The MyCase assigned attorney (user_id) resolves to an Odoo res.users record by email match.
How it maps
If the attorney does not have an Odoo user account, their MyCase ID is stored in x_mycase_former_owner for admin assignment after migration. Unresolved owners are reported before the migration run.
Case.status / case_stage → crm.lead.stage_id
MyCase case status values (Active, Pending, Closed, Archived) map to corresponding Odoo CRM stage IDs.
How it maps
Stage names are mapped value-by-value. If MyCase has custom status labels, Odoo stage names are created to match them — the admin reviews stage colors and probability settings post-migration.
Time Entry → mail.message ( subtype = 'mt_note' )
MyCase time entries become mail.message records attached to the parent crm.lead.
How it maps
Each message preserves the original description, hours, rate, and date as message body text. Billable vs non-billable flags are stored in a custom boolean field x_mycase_billable on the message record. This approach preserves activity history without creating Odoo account.analytic.line records.
- Contactres.partner1:1
- Companyres.partner1:1
- Casecrm.lead1:1
- Case.assigned_attorneycrm.lead.user_idtransformed
- Case.statuscrm.lead.stage_idtransformed
- Time Entrymail.message1:1
+ 6 more in the mapping below
How MyCase and Odoo CRM differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | MyCase | Odoo CRM |
|---|---|---|
| Primary entity model | MyCase organizes everything around Cases (matters) — contacts and companies are secondary properties of a case. A case can exist without a primary contact in MyCase. | Odoo CRM uses crm.lead for opportunities and res.partner for contacts/companies. Leads and partners are standalone records joined by partner_id. A crm.lead without a partner_id is allowed but is treated as incomplete. |
| Contact-company association | MyCase supports N:N contact-to-company relationships natively. One contact can be associated with multiple law firms or clients simultaneously. | Odoo res.partner uses a single parent_id for company membership. Additional company relationships require Account Contact Relations or custom many2many fields on res.partner. |
| Billing model | MyCase has native IOLTA trust accounting, flat-fee billing, and batch invoice generation built directly into the case workflow. | Odoo Accounting is a separate app (requires Odoo Sales or standalone invoicing). Trust accounting requires the Odoo Accounting app configured with dedicated journals and IOLTA accounts. |
| Custom field architecture | MyCase custom fields are defined per-object in settings and stored as key-value properties on the record. Export preserves them as CSV columns. | Odoo custom fields require ir.model.field definitions created in developer mode or via Odoo Studio before data can be written to them. Custom fields must exist before import. |
| Workflow automation engine | MyCase workflows trigger tasks, calendaring, and document automation based on case-stage transitions. Workflows are defined per case-type template. | Odoo automations use Action Rules (ir.actions.server) triggered on write/create events. Server actions can generate tasks, send emails, or update fields. The logic model is entirely different from MyCase's template-based workflows. |
| API access | MyCase API rate-limits at 25 requests per second per client. Full data export requires the Advanced tier ($109/user/month) which includes open API access. | Odoo External API is available via xmlrpc/jsonrpc. API access requires the Odoo Custom Plan (paid); Community edition has no API access for external integrations without custom development. |
| Document storage | MyCase Drive stores documents per case folder. Documents are associated with a case and versioned within that context. | Odoo uses ir.attachment with res_model and res_id linking. Documents can be attached to any model — crm.lead, res.partner, or ir.attachment records — but folder hierarchies are not native. |
MyCase to Odoo CRM field mapping
The 30 most-used fields of 39 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
first_nameContactfirstnameres.partner -
last_nameContactlastnameres.partner -
emailContactemailres.partner -
phoneContactphoneres.partner -
mobile_phoneContactmobileres.partner
| MyCase field | Odoo CRM field | Mapping | Note |
|---|---|---|---|
Contact.first_name | res.partner.firstname | direct | |
Contact.last_name | res.partner.lastname | direct | |
Contact.email | res.partner.email | direct | |
Contact.phone | res.partner.phone | direct | |
Contact.mobile_phone | res.partner.mobile | direct | |
Contact.title | res.partner.title | direct | |
Contact.street_address | res.partner.street | direct | |
Contact.city | res.partner.city | direct | |
Contact.state | res.partner.state_id | direct | |
Contact.zip_code | res.partner.zip | direct | |
Contact.country | res.partner.country_id | direct | |
Contact.created_date | res.partner.x_mycase_created_date | custom_field_required | Odoo overwrites CreatedDate at insert time. Original MyCase create date is preserved as a custom datetime field x_mycase_created_date for reporting continuity. |
Contact.updated_date | res.partner.write_date | direct | |
Contact.mycase_id | res.partner.x_mycase_record_id | custom_field_required | MyCase internal ID stored as a char field for delta-run de-duplication and audit traceability. |
Contact.company | res.partner.parent_id | transformed | MyCase stores the associated company as a contact property. Odoo requires the company to exist as a res.partner first; contacts without a matching company are linked to a default 'Unaffiliated' partner. |
Company.company_name | res.partner.name | direct | |
Company.website | res.partner.website | direct | |
Company.phone | res.partner.phone | direct | |
Company.company_type | res.partner.company_type | direct | |
Company.mycase_id | res.partner.x_mycase_record_id | custom_field_required | MyCase company ID stored for delta-run de-duplication. |
Case.case_name | crm.lead.name | direct | |
Case.case_number | crm.lead.x_mycase_case_number | custom_field_required | Original MyCase case number (e.g., '2024-CIV-042') stored as a custom char field for reference and reconciliation. |
Case.case_status | crm.lead.stage_id | value_mapping | MyCase status pick-list values map to Odoo stage_id. Custom status labels require stage creation in Odoo CRM before migration. |
Case.case_type | crm.lead.x_practice_area | custom_field_required | MyCase practice area or case type (litigation, transactional, estate) maps to a custom selection field on crm.lead. |
Case.assigned_attorney | crm.lead.user_id | transformed | Attorney email resolved to Odoo res.users record. Unmatched attorneys stored in x_mycase_former_owner for post-migration assignment. |
Case.open_date | crm.lead.x_mycase_open_date | custom_field_required | Original case open date preserved as custom datetime field since Odoo create_date reflects migration time. |
Case.close_date | crm.lead.x_mycase_close_date | custom_field_required | Closed case date preserved as custom field for reporting on historical matters. |
Case.description | crm.lead.description | direct | |
Time Entry.hours | mail.message.body (structured) | direct | |
Time Entry.description | mail.message.body | direct |
What to watch for in a MyCase to Odoo CRM migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
MyCase case-type workflow logic has no Odoo CRM equivalent and must be rebuilt
MyCase uses template-based case workflows that auto-generate tasks, calendared deadlines, and document assembly when a case enters a specific stage.
How we handle it
Odoo CRM's automation engine (ir.actions.server) operates on write/create event triggers and has a fundamentally different condition model — it does not understand MyCase's case-type templates. FlitStack exports your MyCase workflow definitions as a JSON schema listing triggers, conditions, and actions. Your Odoo administrator rebuilds them using Odoo Studio server actions or custom Python server actions. This is always a manual step — no automated translation of MyCase automation logic to Odoo is possible.
Odoo ir.model.field definitions must be created before any data loads
Odoo enforces a schema-first model: custom fields must exist as ir.model.field definitions before any data can be written to them.
How we handle it
MyCase stores custom field values as flat key-value properties that export as normal CSV columns. When those columns arrive in Odoo, the fields must already exist or the import silently skips them. FlitStack handles this by scanning all MyCase custom field definitions during the discovery phase, creating the corresponding ir.model.field records via the Odoo API before the migration run, and validating that every column in the export has a target field in Odoo. If a MyCase custom field references a pick-list, the Odoo selection options must also be populated in the same step.
N:N contact-to-company associations collapse to a single parent_id
MyCase allows a single contact to be associated with multiple law firm clients simultaneously — a paralegal working across three matters for three different clients keeps all three company associations on their contact record.
How we handle it
Odoo res.partner uses a single parent_id field for company membership. A second many2many relationship requires the Odoo Account Contact Relations module (available in Odoo Enterprise) or a custom many2many field. FlitStack migrates the primary company association (most-recently-used in MyCase by default) as the parent_id and surfaces the additional company associations as a flagged list in the migration report for your admin to resolve using Odoo's Contact module configuration.
Odoo API access requires a paid plan — Community edition blocks external integrations
MyCase API access requires the Advanced tier ($109/user/month).
How we handle it
Odoo External API access via xmlrpc/jsonrpc requires the Odoo Custom Plan — the Community edition has no supported external API access for automated migration tools. If your Odoo instance is running Community without the Custom Plan upgrade, FlitStack uses Odoo's CSV import via the web interface, which is slower and has lower record-per-batch limits compared to API-based migration. This affects timeline estimates: Community-only imports extend cutover windows by 30–50% due to browser-session constraints.
IOLTA trust accounting and flat-fee billing have no CRM-level migration path
MyCase's IOLTA trust account tracking, operating account balance management, and flat-fee billing rules are practice-management accounting constructs that live entirely outside Odoo CRM.
How we handle it
Odoo does not model IOLTA accounts in its CRM module — those records require the Odoo Accounting app with dedicated journal configuration (IOLTA trust journal, operating journal, and appropriate fiscal positions). FlitStack migrates the trust account metadata and last-known balances as custom notes on the associated res.partner. Your Odoo accountant must configure the accounting journals before those records can become functional.
How the migration runs
Discover MyCase data model and Odoo schema requirements
FlitStack reads MyCase export data via its API (Advanced tier) or Full Data Backup tool, cataloging every object type, custom field definition, and relationship.
What this step covers
Simultaneously, we inspect the target Odoo database to identify installed apps, existing custom fields, and stage configuration. This discovery output is a data map document listing every MyCase field, its Odoo target (res.partner, crm.lead, mail.message, ir.attachment), the mapping type, and any pre-requisite Odoo field creation required. This document is the shared planning artifact between FlitStack and your Odoo administrator before any data moves.
Create Odoo custom fields and stage configuration
Before any data loads, FlitStack creates all required ir.model.field definitions in Odoo via the xmlrpc API — custom fields on res.partner and crm.lead, custom selection values for case type and practice area, and the x_mycase_record_id traceability field on every object.
What this step covers
Simultaneously, we map MyCase case statuses to Odoo stage_id values, creating new CRM stages if the MyCase status labels have no Odoo equivalent. If Odoo Community edition is detected (no API access), this step switches to a manual field-creation guide delivered to your admin with exact field names, types, and selection options to create in Odoo Studio.
Resolve owners and users by email match
MyCase user and attorney IDs are matched to Odoo res.users records by email address.
What this step covers
FlitStack generates a pre-migration owner resolution report listing matched users, unmatched users, and suggested fallback assignments. Your team either creates missing Odoo user accounts or designates a fallback owner before the migration run. No record lands in Odoo without a resolved user_id — records with unresolved owners are held in a staging crm.lead tagged with x_mycase_former_owner for post-migration manual assignment.
Run a sample migration with field-level diff
A representative slice migrates first — typically 200–500 records covering contacts, companies, cases, time entries, and documents across multiple case types.
What this step covers
FlitStack generates a field-level diff comparing source values in MyCase against the destination values in Odoo for every mapped field. You review the diff to verify case number mapping, practice area translation, time entry formatting, and document attachment links before the full run commits. This is the validation gate: if any field-level check fails the acceptance criteria, the mapping is adjusted and the sample re-runs before cutover.
Execute full migration with delta-pickup window
The full migration runs in dependency order: companies (res.partner, company_type = 'company') first, then contacts, then cases (crm.lead) with foreign keys resolving correctly.
What this step covers
Documents and attachments migrate after their parent records are confirmed in Odoo. A delta-pickup window of 24–48 hours runs concurrently with your team's final MyCase data entry, capturing any cases created or modified during the cutover period. FlitStack's audit log records every record operation — insert, update, skip, or error — and one-click rollback is available if reconciliation reveals systematic data issues. After rollback window closes, the audit log is delivered as a CSV for your compliance record.
Deliver workflow export and post-migration rebuild reference
FlitStack exports your MyCase workflow definitions as a structured JSON document covering every automated task template, case-stage trigger, and document assembly rule.
What this step covers
This document is handed to your Odoo administrator as a rebuild specification for Odoo Studio server actions. We do not migrate automations automatically — the logic models are incompatible between platforms. The workflow export includes the exact MyCase UI labels and condition logic so your admin can replicate the business rules in Odoo's action-rule framework without reverse-engineering the original intent from scratch.
MyCase - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
MyCase to Odoo CRM migrations price across the full range depending on record volume, custom field count, and how many Odoo apps are involved. Configurations with fewer than 2,000 records, no custom objects, and a single MyCase subscription tier typically land in the lower range. Firms that use MyCase Advanced tier with extensive custom fields, document attachments exceeding 10GB, or multi-firm structures (where MyCase companies represent separate Odoo databases) push toward the upper range because each additional app or custom field namespace requires separate Odoo field definition work and validation. Billing-related fields (trust accounts, IOLTA) require Odoo Accounting app configuration on top of CRM setup, which adds planning time. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for MyCase to Odoo CRM →Why teams move from MyCase to Odoo CRM
- MyCase is purpose-built for law firms — when a practice expands into inventory, project billing, or non-legal CRM, the platform hits structural limits. Odoo provides a modular ERP that grows with the business without requiring a second tool stack. G2 reviewers who moved to Odoo specifically cited the all-in-one ERP perspective as a reason to consolidate.
- MyCase users on G2 and Capterra report frustration with the one-way QuickBooks sync — deleting a transaction in MyCase does not remove it from QuickBooks, creating reconciliation drift that requires manual correction. Odoo's native Accounting app eliminates the sync layer entirely for firms that want full integration.
- MyCase Advanced tier is priced at $109/user/month (annual) — for firms with 10+ users the annual cost exceeds comparable Odoo Enterprise pricing, especially when Odoo's module bundling covers CRM, Sales, and Accounting under one user plan. Reddit discussions in r/Odoo and r/CRM confirm cost consolidation as a migration driver.
- Odoo Community is free to self-host, giving law firms ownership of their data and infrastructure without per-user SaaS subscription costs. MyCase is fully cloud-hosted with no self-hosted option, which some firms cite as a compliance concern for sensitive client data.
- MyCase notifications and client message workflows depend on a specific UI pattern that changed in recent updates — users in Capterra reviews reported difficulty navigating the new interface for message and document routing, and stated they were evaluating alternatives with more stable UX patterns.
Questions, answered
MyCase to Odoo CRM migration questions
How long does a MyCase to Odoo CRM migration take?
Most MyCase-to-Odoo CRM migrations complete in 48–72 hours of clock time for setups under 10,000 records. Larger firms with 50,000+ records, extensive document archives, or multi-firm MyCase configurations extend to 5–10 days. The longest planning step is creating Odoo custom field definitions and matching MyCase case statuses to Odoo stage_id values — that schema preparation typically takes 2–3 days before the first data record moves.
Will my MyCase case workflows and automated task templates migrate to Odoo?
No. FlitStack AI migrates data and schema only — MyCase case workflows, automated task templates, document assembly rules, and calendaring automations do not transfer. The logic models are fundamentally incompatible: MyCase uses template-based case workflows while Odoo uses ir.actions.server event-triggered action rules. We export your MyCase workflow definitions as a structured JSON rebuild reference so your Odoo administrator can reconstruct them in Odoo Studio.
What happens to MyCase case numbers and case-type data in Odoo CRM?
MyCase case numbers (e.g., '2024-CIV-042') migrate as a custom char field x_mycase_case_number on every Odoo crm.lead record. Practice area and case type (litigation, transactional, estate planning) migrate as a custom selection field x_practice_area. Original case open and close dates are stored in custom datetime fields since Odoo's create_date reflects migration insert time. Your Odoo pipeline stages are mapped to MyCase case statuses value-by-value — if MyCase has custom status labels, Odoo CRM stages are created to match them before the migration run.
Can I migrate MyCase custom fields to Odoo CRM?
Yes. MyCase contact, company, and case custom fields are migrated as Odoo ir.model.field definitions on the corresponding object (res.partner or crm.lead). Each custom field must be created in Odoo before migration data can be written to it — FlitStack handles this by scanning MyCase custom field definitions during discovery and creating the Odoo field records via the Odoo API before the migration run. Field types translate: MyCase text fields become Odoo char fields, pick-lists become selection fields, date fields become date fields.
What happens to MyCase time entries and billing records?
MyCase time entries become Odoo mail.message records attached to the parent crm.lead, preserving the original date, hours, description, and billable/non-billable flag. MyCase invoice records are not migrated as Odoo account.move objects because Odoo invoicing requires chart-of-accounts configuration — instead, MyCase invoice IDs, numbers, and amounts are stored as custom fields on the crm.lead as a reference for reconstruction in Odoo Accounting.
Does the migration affect my MyCase account during cutover?
No. FlitStack AI uses scoped read access on MyCase — your team continues working in MyCase throughout the migration window. A delta-pickup period of 24–48 hours runs concurrently with final data entry, capturing any cases, contacts, or time entries created or modified during cutover. Your MyCase account is read-only for the duration of the migration run and reverts to full access once the delta window closes and data is confirmed in Odoo.
Will MyCase trust account and IOLTA data transfer to Odoo?
Trust account balances, IOLTA transaction history, and flat-fee billing rules do not migrate as functional accounting records because Odoo CRM has no native IOLTA accounting model — that requires the Odoo Accounting app with dedicated journal configuration (IOLTA trust journal, operating journal, and fiscal positions). FlitStack migrates trust account metadata and last-known balances as custom notes on the relevant res.partner for your accountant to reference when configuring Odoo Accounting post-migration.
Why does MyCase to Odoo CRM require a paid Odoo plan for migration?
Odoo External API access via xmlrpc or jsonrpc — which FlitStack uses to write records, create custom fields, and generate the audit log — requires the Odoo Custom Plan. The Community edition has no supported external API for automated migration tools. If your Odoo instance is Community-only, FlitStack falls back to Odoo's native CSV import via the web interface, which has lower record-per-batch limits and extends the cutover window by 30–50%. The Custom Plan is a separate subscription from FlitStack's migration fee.
Related migrations
Odoo implementation
Set up Odoo CRM and migrate into it as one engagement.
See the service → Dynamics 365 to Odoo CRMMapping · history · rollbackFlowlu to Odoo CRMMapping · history · rollbackAttio to Odoo CRMMapping · history · rollbackAct! to Odoo CRMMapping · history · rollbackZendesk Sell to Odoo CRMMapping · history · rollbackSuiteCRM to Odoo CRMMapping · history · rollback MyCase to HubSpotMapping · history · rollbackSources: official documentation
- Export and import data — Odoo 19.0 documentation
- Import products — Odoo 19.0 documentation
- Odoo Online programmatic throughput limits — Odoo Forum
- Data Cleaning — Odoo 19.0 documentation
- Datetime field reference — Odoo 19.0 documentation
- Upload size limit in Odoo — Odoo Forum (128 MiB cap)
- Fields and widgets — Odoo 19.0 documentation (Studio)
Get a quote
Moving from MyCase to Odoo CRM?
Tell us roughly how many records and objects you have. We scope the mapping and the Odoo CRM setup with you, then send a quote.
Get a quote