CRM migration

Migrate from Centerbase to Odoo CRM

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

Centerbase logo

Centerbase

Source

Odoo CRM

Destination

Odoo CRM logo

Compatibility

92%

11 of 12

objects map 1:1 between Centerbase and Odoo CRM.

Complexity

BStandard

Timeline

1–2 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Centerbase organizes data around a matter-centric model: Clients hold company-level data, Contacts are people linked to clients, and Matters are the project containers that carry billing, time entries, and document attachments. Odoo CRM uses a flattened res.partner model for contacts and companies, crm.lead for opportunities, and stores activities as mail.message records. The migration maps Centerbase clients and contacts to res.partner records — designating one primary contact per client — and maps Matters to crm.lead records with matter-type and billing data stored in custom fields on the lead. Activities, documents, and custom fields transfer directly; workflows, billing engines, and matter-specific automations do not have Odoo equivalents and must be rebuilt. We use Centerbase's REST/Web API for extraction and Odoo's XML-RPC interface for import, running within a scoped read window so your team keeps working in Centerbase throughout. A delta-pickup phase captures any matters or contacts created or modified during cutover. This ensures data continuity and supports a smooth transition to the new CRM.

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

Centerbase logo

Centerbase

What's pushing teams away

  • Platform updates occasionally break existing workflows and functionality, requiring support intervention to restore — a pattern confirmed across multiple G2 reviews citing frustration with update-related regressions.
  • Reporting is difficult to navigate and often fails to produce the exact output firms need, with specific firm requirements frequently unmet by the built-in report writer.
  • Inconsistent customer support response times and quality create friction when issues arise, particularly during or after the implementation phase.
  • The interface is described as overwhelming by new users with a steep learning curve that requires significant training investment before staff can operate efficiently.

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

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

Centerbase

Client

maps to

Odoo CRM

res.partner

1:1
Fully supported

Centerbase Clients map to Odoo res.partner records with partner gtype=company. Legal entity name goes in name field. Industry, annual revenue, employee count map to Odoo partner fields directly. Billing address and shipping address preserved as partner contact addresses. All addresses retain their original labels for straightforward identification.

Centerbase

Contact

maps to

Odoo CRM

res.partner

1:1
Fully supported

Centerbase Contacts map to Odoo res.partner records with partner gtype=contact. Each contact links to its primary client partner via parent_id. When a client has multiple contacts, all map to the same parent_id partner with individual partner records as children. This structure mirrors the original hierarchy accurately.

Centerbase

Contact (Client primary flag)

maps to

Odoo CRM

res.partner (parent_id)

many:1
Fully supported

When a Centerbase contact is marked as the primary client contact, that partner record becomes the default addressee on the parent client partner in Odoo. The primary flag is preserved as a boolean field on the partner record. This ensures the main contact is readily identifiable in Odoo.

Centerbase

Matter

maps to

Odoo CRM

crm.lead

1:1
Fully supported

Centerbase Matters map to Odoo crm.lead records. Matter name becomes lead name (display_name). Matter status maps to crm.stage via value mapping per matter type. Matter type (e.g., Litigation, Transaction, Corporate) becomes a custom selection field on the lead. This preserves the original categorization for reporting and segmentation.

Centerbase

Matter (Billing amount)

maps to

Odoo CRM

crm.lead (x_billing_amount)

1:1
Fully supported

Odoo CRM does not natively track billing amounts on leads. We create a custom float field x_billing_amount on crm.lead and migrate the matter's total billing amount for reference. Full billing history requires separate Odoo Accounting migration. This allows finance teams to see indicative billing totals without full accounting setup.

Centerbase

Matter (Billing status)

maps to

Odoo CRM

crm.lead (x_billing_status)

1:1
Fully supported

Matter billing status (Billed, Unbilled, Pending) migrates as a custom selection field x_billing_status on crm.lead. This preserves the billing state for finance-side reconciliation without requiring Odoo Accounting setup. It provides immediate visibility into the billing state for each lead and supports reporting during the transition period.

Centerbase

Activity (Call, Meeting, Email, Task)

maps to

Odoo CRM

mail.activity + mail.message

1:1
Fully supported

Centerbase activities map to Odoo mail.activity records linked to crm.lead. Activity type (call, meeting, email) maps to activity_type_id via value mapping. Subject and notes map to summary and note fields. Original timestamps and owner preserved from source. This maintains complete activity history for future follow-ups.

Centerbase

Document / Attachment

maps to

Odoo CRM

ir.attachment

1:1
Fully supported

Documents attached to Centerbase matters or contacts are downloaded and re-uploaded as Odoo ir.attachment records linked to the corresponding crm.lead or res.partner. File content, original filename, and create date are preserved. Inline images in notes are extracted and re-hosted as attachments.

Centerbase

Centerbase User / Owner

maps to

Odoo CRM

res.users

1:1
Fully supported

Centerbase owners resolve to Odoo res.users records by email address match. Unmatched owners are flagged before migration so your Odoo admin can create user accounts or assign a fallback owner. User records themselves do not migrate — they are matched against existing Odoo users.

Centerbase

Custom Field (Matter)

maps to

Odoo CRM

crm.lead (Studio custom field)

1:1
Fully supported

Any custom fields defined on Matter objects in Centerbase are recreated as Studio-defined custom fields on crm.lead in Odoo. Field type is mapped: text to char, number to float, date to date, pick-list to selection. Long-text fields become odoo.text fields.

Centerbase

Custom Field (Contact, Client)

maps to

Odoo CRM

res.partner (Studio custom field)

1:1
Fully supported

Custom fields on Client and Contact objects in Centerbase are recreated as Odoo Studio custom fields on res.partner. Relationship-type custom fields (e.g., linking a contact to a matter) are translated to Odoo many2one or many2many field types as appropriate. We ensure field labels and help texts are preserved for user clarity.

Centerbase

Workflow / Automation

maps to

Odoo CRM

None

1:1
Fully supported

Centerbase workflows, automated stages, matter checklists, and triggers have no direct Odoo CRM equivalent. Odoo uses Automated Actions and Server Actions which are destination-side constructs. We export your workflow definitions as a reference document for your Odoo admin to rebuild.

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.

Centerbase logo

Centerbase gotchas

High

Images do not transfer in Centerbase report and document exports

Medium

Workflow definitions require manual rebuild on non-Centerbase destinations

Medium

Billing records carry nested LEDES codes and origination data that require explicit mapping

Medium

Trust account three-way reconciliation rules do not transfer automatically

Low

Platform update cycles can break migrated workflows at the destination

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

  • Matter billing data has no native home in Odoo CRM

    Centerbase bakes billing and time-tracking into the matter object — total billed, unbilled amounts, LEDES codes, and billing status are all stored directly on the matter record. Odoo CRM intentionally separates billing into the Accounting application (a distinct Odoo module that must be installed and configured separately). If you rely on billing data for pipeline decisions, that information needs to land in Odoo Accounting via a separate migration pass. We migrate billing_amount and billing_status as custom fields on crm.lead for reference, but full billing history requires Odoo Accounting setup and a dedicated accounting-data migration.

  • Centerbase Client-Contact N:N collapses to Odoo parent-child tree

    Centerbase allows a contact to be associated with multiple clients and a client to have multiple contacts, with each contact holding a primary-flag per client. Odoo res.partner collapses this into a parent-child hierarchy: the client becomes a partner gtype=company, contacts become child partners linked via parent_id. The N:N relationship means we must choose one primary contact per client for the parent_id assignment and surface other contacts as additional child partners. Clients with zero contacts become standalone company partners with no children.

  • Centerbase workflows require complete Odoo-side rebuild

    Centerbase's workflow engine generates automated tasks, stage-based triggers, and matter checklists that are tightly coupled to the matter lifecycle. Odoo CRM uses a completely different automation model: Automated Actions (triggers on write/create), Server Actions (Python-based), and res.partner-based Action Rules. There is no migration path — workflow definitions export as a reference PDF and your Odoo admin rebuilds them using Odoo's automation tools. Sequence and stage-based routing logic does not carry over automatically.

  • Odoo API access for import requires Custom plan or Community workaround

    Odoo's XML-RPC interface — the standard import mechanism for bulk record creation — requires the External API module which is available on Odoo Custom (Enterprise) plan only. Odoo Community edition does not include External API access out of the box. If you are on Community, we use Odoo's CSV import with the base_import module or a programmatic load via direct database access. Community import has record-count and field-type limitations that affect which fields can be loaded in a single pass.

  • Matter type taxonomy requires Odoo pipeline pre-configuration

    Centerbase matter types (e.g., Litigation, Transaction, Corporate, Compliance) function as matter categories that affect billing rates, workflow assignment, and team routing. Odoo CRM uses crm.team for team routing and crm.stage for pipeline lanes, but stage scoping per matter type requires either multiple pipelines with separate stages or a custom field on the lead to preserve the matter type label. Without pre-configuration, all matter types land in a single Odoo pipeline with identical stage names, losing the type distinction your team relies on.

Migration approach

Six steps for a successful Centerbase to Odoo CRM data migration

  1. Extract Centerbase data via REST/Web API

    We authenticate against Centerbase using your API credentials (or the .NET client proxy if applicable) and export all clients, contacts, matters, activities, and documents. Custom field definitions are read from Centerbase Settings and catalogued for Odoo Studio recreation. Export runs in scoped read-only mode — no records are modified in Centerbase during this phase. We also capture relationship metadata to preserve hierarchy during the migration.

  2. Configure Odoo CRM schema: stages, teams, custom fields

    Before any data lands, we create the crm.lead custom fields (matter_type, billing_amount, billing_status, original_create_date, source_system_id), configure crm.stage lanes to match Centerbase matter status values, and set up crm.team records for each Centerbase office or department. If you are on Odoo Community, we configure base_import settings for the import pass. This schema plan is delivered for your review before we touch Odoo.

  3. Match owners and users by email

    Centerbase owners are resolved against Odoo res.users records by email address. Unmatched owners are flagged in a pre-flight report so your Odoo admin creates the user accounts or assigns a fallback owner before the migration runs. No lead lands without an assigned Odoo user. This step ensures that every opportunity has a clear owner and that reporting visibility is maintained from day one in the new CRM.

  4. Run sample migration with field-level diff

    A representative sample — typically 100–300 records covering clients, contacts, matters, and activities — migrates first. We generate a field-level diff showing source value vs. destination value for every mapped field so you can verify stage mapping, custom field population, and owner resolution before the full run commits. You sign off on the sample before we proceed. The diff report highlights any missing mappings or data discrepancies for immediate correction.

  5. Execute full migration with delta-pickup window

    Full data load runs against Odoo. After the main load completes, a delta-pickup window (24–48 hours) captures any records created or modified in Centerbase during the cutover window. Every operation is logged in an audit trail. One-click rollback is available if reconciliation fails. After delta-pickup, your Centerbase account becomes read-only and Odoo is your active system. We also perform a final validation against source totals to confirm completeness.

Platform deep dives

Context on both ends of the pair

Centerbase logo

Centerbase

Source

Strengths

  • All-in-one cloud platform consolidates practice management, billing, and accounting without requiring external accounting software.
  • Deep customization of fields, workflows, and matter structures accommodates firm-specific processes at scale.
  • Legal-specific features including IOLTA trust accounting, LEDES export, and origination fee tracking meet bar compliance requirements.
  • Certified partner onboarding with structured implementation phases reduces risk on migration from legacy systems like Time Matters.
  • Custom report writer with cross-database export and import enables firms to move reporting templates between environments.

Weaknesses

  • Steep learning curve and overwhelming interface require significant training investment before staff productivity is achieved.
  • Platform updates occasionally break existing functionality, requiring support intervention to restore normal operations.
  • Inconsistent customer support response times create friction during issue resolution, particularly post-implementation.
  • Reporting is difficult to navigate and frequently fails to deliver the exact output firms need without custom report work.
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. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • 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

    Centerbase: Not publicly documented..

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Centerbase-to-Odoo CRM migrations complete in 1–2 weeks for setups with fewer than 5,000 records and clean, well-structured data. Complex migrations with multiple matter types, extensive custom fields, and activity history spanning years extend to 3–5 weeks. Odoo pipeline and custom-field pre-configuration adds 3–5 days to the planning phase before data moves. We also provide a detailed project timeline and status updates throughout the process.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Centerbase.
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