CRM migration

Migrate from SimplyConvert to Odoo CRM

Field-level mapping, validation, and rollback between SimplyConvert and Odoo CRM. We move data and schema; workflows are rebuilt natively in Odoo CRM.

SimplyConvert logo

SimplyConvert

Source

Odoo CRM

Destination

Odoo CRM logo

Compatibility

100%

13 of 13

objects map 1:1 between SimplyConvert and Odoo CRM.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

SimplyConvert is a purpose-built legal-intake CRM focused on mass-tort and personal-injury case workflows — its primary objects are Client (the contact record), Case (the matter record), and Referral (the intake source). SimplyConvert's pricing model bills per signed-case event, which becomes unpredictable at volume. Odoo CRM uses crm.lead as its unified lead/opportunity model, res.partner for contacts and companies, and stores stage definitions in crm.stage. We map SimplyConvert Client records to res.partner entries, Case records to crm.lead with a custom x_case_type Char field, and SimplyConvert's referral-source and intake-channel properties to custom fields on crm.lead. Custom fields (statute of limitations, venue, claim amount, case status) require Odoo Studio pre-creation before data lands. Automations — SimplyConvert's case-stage notification triggers and referral routing rules — do not migrate and must be rebuilt in Odoo's server actions and automated actions. We sequence the migration so res.partner records exist before crm.lead records (foreign-key dependency via Odoo's partner_id field), run a sample migration against 50–100 records with field-level diff, then execute the full run with a 24–48h delta pickup for any cases opened during cutover.

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

SimplyConvert logo

SimplyConvert

What's pushing teams away

  • Per-conversion pricing model creates unpredictable and escalating costs as claimant volume grows in active litigations
  • Narrow focus on mass tort intake makes the platform unsuitable for firms with diverse practice areas requiring broader case management
  • Small vendor footprint with 23 employees and ~$1M revenue raises long-term support and platform stability concerns
  • Limited third-party integrations beyond native API constrains how SimplyConvert data connects to downstream accounting, e-billing, or e-discovery tools
  • Custom reporting insufficient for firms managing multiple simultaneous litigations needing cross-case analytics and settlement benchmarking

Choosing

Odoo CRM logo

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 SimplyConvert objects map to Odoo CRM

Each row shows how a SimplyConvert 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.

SimplyConvert

Client

maps to

Odoo CRM

res.partner

1:1
Fully supported

SimplyConvert Client maps directly to Odoo res.partner. The res.partner record stores contact name, email, phone, address, and company association. SimplyConvert clients without a linked company map to res.partner entries with no parent_id; Odoo treats standalone contacts as partners with category_id (tags) for segmentation.

SimplyConvert

Case

maps to

Odoo CRM

crm.lead

1:1
Fully supported

SimplyConvert Case is the core matter record and maps 1:1 to Odoo crm.lead. The crm.lead model in Odoo holds both lead and opportunity states; we set type='opportunity' for all migrated cases so they appear in the pipeline kanban view. The case name becomes crm.lead name field; case description maps to crm.lead description.

SimplyConvert

Referral

maps to

Odoo CRM

crm.lead (custom fields)

1:1
Fully supported

SimplyConvert's Referral object carries source, campaign, staff assignment, and intake timestamp. We collapse these into two custom Char fields on crm.lead: x_referral_source and x_intake_channel. The original Referral object creation date is preserved in x_referral_date for attribution continuity. Odoo Automated Actions can be configured to set these fields based on lead source rules post-migration.

SimplyConvert

Case.claim_type

maps to

Odoo CRM

crm.lead.x_claim_type (custom field)

1:1
Fully supported

SimplyConvert stores matter-type strings (e.g., 'Personal Injury', 'Mass Tort', 'Employment') on the Case record. Odoo CRM has no native claim_type equivalent. We create x_claim_type as a Selection field on crm.lead before migration, populated with the distinct claim_type values found in the source dataset. Admins can adjust the selection list post-migration.

SimplyConvert

Case.statute_of_limitations_date

maps to

Odoo CRM

crm.lead.x_sol_date (custom field)

1:1
Fully supported

SimplyConvert captures SOL dates on Case records — critical for personal-injury and mass-tort intake workflows. Odoo CRM has no native SOL field. We create x_sol_date as a Date field on crm.lead. During migration we surface SOL-date records in a dedicated Odoo view so attorneys can monitor deadlines; Odoo's calendar integration can be wired to generate reminders post-migration.

SimplyConvert

Case.claim_amount

maps to

Odoo CRM

crm.lead.planned_revenue

1:1
Fully supported

SimplyConvert stores the estimated or filed claim amount on the Case record. Odoo's closest monetary field is crm.lead planned_revenue (a Monetary field tied to the company currency). We map claim_amount → planned_revenue. Where SimplyConvert uses a placeholder zero for pre-assessment cases, we leave planned_revenue blank to avoid skewing Odoo's revenue forecasts.

SimplyConvert

Case.intake_channel

maps to

Odoo CRM

crm.lead.x_intake_channel (custom field)

1:1
Fully supported

SimplyConvert tracks how a case entered the funnel ( chatbot, referral partner, organic, paid search). We create x_intake_channel as a Selection field on crm.lead and map each distinct source value to an Odoo selection option. Post-migration, Odoo's utm_source / utm_medium fields can replace this with standard attribution tracking.

SimplyConvert

Case.assigned_staff

maps to

Odoo CRM

res.users (via crm.lead.user_id)

1:1
Fully supported

SimplyConvert Case records carry an assigned staff member (the attorney or paralegal handling the matter). We match SimplyConvert staff email addresses against Odoo res.users records by email. Unmatched staff are flagged before migration; firms either invite them to Odoo first or assign their cases to a designated fallback user to avoid orphaned records.

SimplyConvert

Case.venue

maps to

Odoo CRM

crm.lead.x_venue (custom field)

1:1
Fully supported

Mass-tort and personal-injury firms track the court venue (county, district, state) for each case. Odoo CRM has no native venue field. We create x_venue as a Char field on crm.lead and populate it with the venue string from SimplyConvert. For high-volume jurisdictions, this can be promoted to a Selection field with the top 10–20 venues pre-loaded.

SimplyConvert

Document / Attachment

maps to

Odoo CRM

ir.attachment

1:1
Fully supported

SimplyConvert stores documents per case (intake forms, medical records, correspondence). We re-upload these as ir.attachment records linked to the corresponding crm.lead via res_model='crm.lead' and res_id=<lead_id>. Odoo's document management (Documents app) can be activated post-migration to provide a richer file library for each lead.

SimplyConvert

Case.case_status

maps to

Odoo CRM

crm.stage

1:1
Fully supported

SimplyConvert Case records carry a status field: Intake, Open, Under Review, Closed, Settled. Odoo CRM stages are defined per sales team in crm.stage. We create a mapping table: SimplyConvert 'Intake' → Odoo 'New', 'Open' → 'Qualified', 'Under Review' → 'Proposal', 'Closed' → 'Won', 'Settled' → 'Lost'. Stage names are configurable per firm's Odoo team settings.

SimplyConvert

Case.create_date

maps to

Odoo CRM

crm.lead.create_date

1:1
Fully supported

Odoo sets create_date at record insertion time by default. We preserve the original SimplyConvert case creation timestamp in x_original_create_date as a custom Datetime field so reporting continuity is maintained. This is critical for law firms tracking intake volume over time.

SimplyConvert

Client.email

maps to

Odoo CRM

res.partner.email

1:1
Fully supported

Direct email field map. Odoo validates email format on res.partner; invalid formats are flagged and corrected before migration runs. Duplicate emails (multiple SimplyConvert clients sharing one address) are surfaced for manual resolution — Odoo enforces email uniqueness at the partner level by default.

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.

SimplyConvert logo

SimplyConvert gotchas

High

Per-conversion billing requires conversion-status audit before migration

High

No bulk export endpoint forces pagination under strict rate limits

Medium

No standalone Contact object requires structural flattening

Medium

API key generation requires direct vendor contact

Low

Named litigation groupings not exposed as filterable objects

Odoo CRM logo

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

Pair-specific challenges

  • Odoo requires custom fields pre-created before bulk data insertion

    Odoo stores field definitions in ir.model.fields — custom fields on crm.lead must exist in the schema before any records land. FlitStack generates an Odoo Studio field-creation plan (x_claim_type, x_intake_channel, x_venue, x_sol_date, x_original_create_date, x_source_client_id, x_source_case_id) that your Odoo admin applies before migration runs. If fields are missing, the CSV import skips those columns silently, causing data loss on those properties. We validate field existence against Odoo's ir.model.fields before the migration commits, but schema setup is a prerequisite that must be completed in your Odoo environment first.

  • SimplyConvert case status maps to Odoo stages by value — stage IDs differ per team

    Odoo CRM stages are scoped to crm.team — the same stage name (e.g., 'New') has a different stage_id for each sales team in Odoo. SimplyConvert's global case_status field (Intake, Open, Closed) needs a value-mapping table resolved per Odoo team after your team is created. If your firm uses multiple Odoo CRM teams (e.g., litigation team vs. intake team), each team needs its own stage-ID mapping. FlitStack resolves stage IDs at migration runtime using the target team's pipeline configuration, but teams must be set up before the migration plan is finalized.

  • Statute of limitations dates require a dedicated Odoo calendar or deadline view

    SimplyConvert surfaces SOL dates as a case property that attorneys monitor manually. Odoo CRM has no native deadline-tracking for legal SOL dates — the field migrates but Odoo won't generate automatic reminders. Post-migration, your Odoo admin needs to configure either an Odoo Planned Activity on each lead's x_sol_date or an Odoo Calendar event reminder. We include the SOL date in x_sol_date but the reminder logic must be wired separately using Odoo's scheduled actions. This is not a data-loss issue but a workflow-gap that requires post-migration configuration.

  • Document re-upload rate limited to 200 files/minute on Odoo XML-RPC

    SimplyConvert's document upload API supports 200 uploads per minute. Odoo's XML-RPC write endpoint is also subject to instance-level throttling — for heavy document volumes (hundreds of files per case across thousands of cases), the migration paces writes to stay within Odoo's request limits. For firms with more than 10,000 attachments, this can extend the document-migration phase by several hours. We recommend activating Odoo's attachment storage on a dedicated file path (filestore) before migration to avoid database bloat, and we flag any files that exceed Odoo's 25MB per-file limit for manual handling.

  • Referral object collapses into crm.lead custom fields — campaign attribution is best-effort

    SimplyConvert's Referral object stores rich attribution: source partner, campaign ID, referral date, staff assignment, and referral notes. Odoo CRM has no separate Referral object. We map the referral source and campaign into crm.lead custom fields (x_referral_source, x_intake_channel). The referral date and staff notes migrate as plain text in x_referral_source. If Odoo's native Campaign tracking is active (crm.campaign model), we can upgrade to a proper campaign_id link — but this requires the CRM Campaign module to be installed and configured in your Odoo instance before migration runs.

Migration approach

Six steps for a successful SimplyConvert to Odoo CRM data migration

  1. Audit SimplyConvert data volume and custom field inventory

    Before any schema work, FlitStack pulls a full export from SimplyConvert via its API: all Client records, Case records, Referral records, and document metadata (file names, URLs, sizes). We count distinct values for claim_type, intake_channel, case_status, and referral_source to pre-build the Odoo selection-option lists. We also flag records with missing required fields (clients without email, cases without a linked client) for your team to clean or confirm before migration. This audit typically runs within 4–8 hours of access being granted.

  2. Create Odoo custom fields on crm.lead via Odoo Studio or data file

    Using the field inventory from Step 1, FlitStack generates an Odoo CSV data file (for Settings > Technical > Models > Import) that creates all required custom fields: x_claim_type, x_intake_channel, x_venue, x_sol_date, x_original_create_date, x_source_client_id, x_source_case_id. Your Odoo admin applies this file (or creates fields manually in Odoo Studio) before the migration window. We validate field existence via Odoo's ir.model.fields API before proceeding. If Odoo's Campaign module is active, we also configure the campaign_id link for referral attribution.

  3. Resolve SimplyConvert staff to Odoo res.users by email

    SimplyConvert's assigned_staff field carries staff email addresses. FlitStack queries Odoo's res.users table by email to resolve each SimplyConvert staff member to a corresponding Odoo user ID. Staff without a matching Odoo account are listed in a pre-migration report — your team either invites them to Odoo or designates a fallback user to receive those cases. No Case migrates without a resolved user_id; orphan prevention is enforced before the migration run commits.

  4. Migrate res.partner records first, then crm.lead with foreign-key validation

    Odoo's crm.lead model requires a valid partner_id (res.partner) for most lead views. We sequence the migration: (1) all Client records → res.partner; (2) all Case records → crm.lead with partner_id lookup from Step 3; (3) all document ir.attachment records linked to the newly created crm.lead IDs. Documents are uploaded last to avoid dangling references. We run a sample migration of 50–100 records first and generate a field-level diff comparing source values to Odoo read-back values — your team reviews this before the full run commits.

  5. Execute full migration with delta-pickup window and audit log

    The full migration runs against your Odoo instance. FlitStack maintains a full audit log of every record created: source record ID, destination record ID, field values written, and timestamp. A delta-pickup window (24–48 hours from migration start) captures any new SimplyConvert cases or clients opened during the cutover. After delta-pickup, we run a reconciliation report comparing record counts and a random-sample field-level check. If reconciliation passes, the migration is accepted. If not, one-click rollback reverts all FlitStack-created records from the Odoo database.

Platform deep dives

Context on both ends of the pair

SimplyConvert logo

SimplyConvert

Source

Strengths

  • Purpose-built for mass tort claimant intake with chatbot, TDP scoring, and claim form population in a single workflow
  • ABA-recognized legal tech innovator with lawyer-founded development team understands litigation-specific data requirements
  • Integrated referral platform and CaseHQ client portal consolidate intake and client-facing communication
  • Real-time case notifications and lead ranking directly support settlement-focused case management priorities
  • Per-conversion pricing aligns cost with firm revenue for high-volume litigations with clear intake-to-contract conversion

Weaknesses

  • Pay-per-conversion billing creates unpredictable and escalating costs as claimant volume grows across active litigations
  • Narrow mass tort specialization unsuitable for firms managing diverse practice areas beyond claimant intake
  • Small vendor footprint (23 employees, ~$1M revenue) raises long-term stability and support-capacity concerns
  • No dedicated bulk export API; large case histories require pagination through the 300 req/min List Cases endpoint
  • Limited documented API coverage for non-Case objects including Contacts, Users, and custom objects
Odoo CRM logo

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.

Complexity grading

How hard is this migration?

Standard CRM migration. All 8 core objects map 1:1 between SimplyConvert and Odoo CRM.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across SimplyConvert and Odoo CRM.

  • Object compatibility

    A

    All 8 core objects map 1:1 between SimplyConvert and Odoo CRM.

  • 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

    SimplyConvert: 300 req/min for List Cases; 2000 req/min for Get Case and Create Case; 200 req/min for Upload Documents and Download Documents; 2000 req/min for all unspecified endpoints.

  • Data volume sensitivity

    B

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

Estimator

Estimate your SimplyConvert to Odoo CRM 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 SimplyConvert to Odoo CRM data migrations

Answers to the questions buyers ask most during SimplyConvert to Odoo CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your SimplyConvert to Odoo CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most SimplyConvert-to-Odoo CRM migrations complete in 24–72 hours for firms with under 25,000 total records (clients, cases, referrals). The longest single step is Odoo schema setup — creating custom fields on crm.lead via Odoo Studio or data file — which takes 2–4 hours depending on field count. Document re-upload runs concurrently with a 200/minute Odoo API rate limit; large attachment volumes (10,000+ files) can extend the document phase by several hours. Firms with over 25,000 records or complex multi-team Odoo setups typically plan for 7–10 days including delta-pickup and reconciliation.

Adjacent paths

Related migrations to explore

Ready when you are

Move from SimplyConvert.
Land in Odoo CRM, 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