Migrate from MaxCredible to Odoo CRM

MaxCredible Debtors map directly to Odoo CRM Partners. Debtor contact details, address information, and payment behavior history transfer as Partner fields. The debtor's credit risk score from MaxCredible migrates to a custom Partner field (x_maxcredible_credit_score) with the effective date preserved in x_credit_score_date. We request a sample export of debtor records during discovery to validate field coverage before migration because MaxCredible does not publish a public field schema.

MaxCredible Invoices map to Odoo Account Move records with type = out_invoice. The invoice amount, due date, and status (open, paid, overdue) transfer to amount_total, invoice_date_due, and payment_state respectively. We map the debtor reference to Partner (res.partner) via the MaxCredible debtor-to-invoice foreign key. Odoo's Receivable account on the invoice must be configured to match the customer's chart of accounts before import.

MaxCredible Credit Notes map to Odoo Account Move with type = out_refund. The credit note is linked to the original invoice via Odoo's reconcile mechanism, ensuring net receivable balance is correctly reflected. If MaxCredible tracks credit note reason codes, we map them to Odoo's credit note reason field or a custom move line label.

MaxCredible Reminders (time-based tasks triggered by invoice aging) map to Odoo Mail Activity records of type = task, linked to the invoice Partner and the related Account Move. The reminder trigger logic (aging thresholds, escalation rules) is documented as workflow logic rather than migrated as automation code. We export reminder body copy and timing parameters so the customer can rebuild the triggering logic in Odoo CRM activities or a custom module.

The MaxCredible receivables ledger aggregates open items per debtor. We extract the ledger as a structured dataset and map it to Odoo Account Move Lines on the configured Receivable account. The ledger-to-move-line mapping preserves the aging buckets (current, 30, 60, 90+ days) if MaxCredible exposes them, otherwise we compute aging from invoice_date_due at migration time.

MaxCredible email communication logs migrate to Odoo Partner chatter as Mail Message records. The email body, subject, timestamp, and sender/recipient transfer. Email template references from MaxCredible's tone-of-voice settings are exported as template body documentation (see Tone-of-Voice Template mapping). Odoo does not support a native email engagement timeline with open/click tracking without Odoo Email Marketing; we document this limitation.

MaxCredible SMS logs migrate to Odoo as documented records (SMS delivery is an Odoo paid add-on or third-party module). We transfer message body, timestamp, and carrier metadata where available. Odoo SMS requires the sms module to be installed; if it is not, we deliver SMS logs as a structured CSV with the partner reference for manual entry or batch upload. Channel-specific carrier metadata (delivery receipts, error codes) is normalized into a custom field.

MaxCredible WhatsApp logs include thread context not natively supported in Odoo CRM. We transfer the message body, timestamp, and contact reference. Thread-level grouping (which messages belong to the same conversation) is exported as a custom field x_whatsapp_thread_id for display purposes. Odoo WhatsApp integration is a third-party module; we document its availability and recommend evaluation if rich WhatsApp context is required.

MaxCredible tone-of-voice templates define branded communication style across channels. These are stored as MaxCredible-specific platform configuration, not structured data. We export template body copy and variable placeholders as a written template inventory document. The customer recreates these in Odoo's Email Template editor (Marketing > Email Templates) using the exported body copy. Template migration as code is not supported.

MaxCredible's AI-driven credit risk score migrates as a static custom field (x_credit_score) on Partner. The score value and its effective date transfer. The underlying behavioral dataset that produces the score (payment timing history, dispute frequency, DSO trajectory) is not exposed by MaxCredible's API and cannot be migrated. We recommend recalibrating credit risk in Odoo using Odoo Accounting's payment term analysis, aged receivables reports, and any available payment history data. The custom field must be created in Odoo before migration.

MaxCredible's XML ERP integrations for Oracle and SAP are MaxCredible-specific configurations that do not transfer to Odoo. We document the integration architecture (mapping rules, sync frequency, data flow) during discovery. If the customer continues using Oracle or SAP, they configure Odoo's native accounting connectors or partner integrations separately. MaxCredible's XML schema is proprietary and not publicly documented; we request sample XML files from the customer during scoping to understand the exchange format.

MaxCredible Tableau report definitions are stored in Tableau, not MaxCredible. These cannot migrate directly to Odoo. We deliver a written report inventory documenting each MaxCredible Tableau report's metrics, filters, and data sources. The customer's BI team rebuilds these in Odoo Reporting, Odoo Analytics, or reconnects Tableau to the new Odoo data source (via Odoo's external database connection or a data warehouse pipeline). Custom fields created in Odoo during migration must be added to Tableau's data source post-migration.

MaxCredible supports user-defined fields on core objects. We extract the full custom field schema (field name, type, associated object, current values) during discovery. Each custom field must be recreated in Odoo as an ir.model.field before data import. We provide a field creation checklist with the correct Odoo field type mapping (text to char or text, number to float or integer, date to date, etc.). Custom field data migrates after the destination field is created.

MaxCredible user accounts (name, email, role) map to Odoo res.users. We extract user records and match by email against the destination Odoo instance. The customer's Odoo admin provisions the user accounts (active or inactive depending on whether the MaxCredible user is still active) before record migration begins. Role mapping is directional: MaxCredible roles translate to Odoo access rights groups manually.

MaxCredible automated workflows trigger actions based on invoice aging and debtor segments. We document every active workflow during discovery: trigger conditions, actions, delays, and debtor segment rules. Workflows are MaxCredible-specific and cannot be exported as Odoo automation rules. We deliver a written workflow inventory with recommended Odoo automation equivalents (Odoo Studio automations, server actions, or scheduled actions) for the customer's admin or Odoo partner to rebuild post-migration.

Documents linked to debtors or invoices in MaxCredible (contracts, proof of delivery, correspondence PDFs) migrate to Odoo ir_attachment records linked to the corresponding Partner or Account Move. We extract binary attachments and store them alongside migrated records. File format compatibility is validated; Odoo supports PDF, DOC, DOCX, XLS, XLSX, PNG, JPG, and others. We flag any non-standard formats during scoping.