Migrate from OneSuite to Odoo CRM

OneSuite Client records map directly to Odoo Contact with a partner_id link to the same record as a Company (res.partner with is_company=True). We extract the primary contact role from OneSuite's Client data and set the contact's function field accordingly. Client revenue data, social links, and ICP status migrate as typed Odoo fields or custom fields defined in Odoo Studio before migration. The clientTier slug from OneSuite (e.g., tierOne) remaps to a custom selection field that we pre-create on the res.partner model.

OneSuite Leads map to Odoo crm.lead with the pipeline stage name preserved in the stage_id field. Lead source attribution and scoring values migrate to the Odoo lead's source and priority fields. We create the Odoo pipeline stages matching OneSuite's stage names and order before the Lead import begins. Scores exceeding typical ranges are stored as a custom float field since Odoo's standard priority field is a selection.

If the customer wants Leads pre-converted to Opportunities, we create Opportunities from Leads during migration by setting the partner_id (Contact/Company) lookup, the planned_revenue amount, and the stage_id matching OneSuite's deal stage. The Lead-to-Opportunity conversion in Odoo also creates a lead_id link; we preserve the original OneSuite lead_id in a custom field for audit trails. This step requires the Odoo CRM app to be installed and the pipeline stages to be pre-created.

OneSuite Projects map to Odoo project.project records if the Odoo Project app is active, or to project.task records if only the CRM app is installed. The Client-to-Project relationship in OneSuite becomes the partner_id on the Odoo project or task. Project milestones map to Odoo project milestone records if the Odoo version supports them; otherwise they are stored as task names with a milestone custom field. We flag any Projects with automation triggers that cannot be replicated automatically.

OneSuite Invoices map to Odoo account.move records with move_type='out_invoice'. We map line items, tax rates, payment status, and currency directly. Multi-currency invoices require the Odoo Accounting app and multi-currency configuration to be active. We flag any Invoices with complex discount rules, custom tax jurisdictions, or Stripe/Quickpay payment metadata that may require manual reconciliation on the Odoo side. Paid status migrates with the payment reconciliation recorded against the bank statement.

OneSuite Documents associated with Clients or Projects migrate as Odoo ir.attachment metadata records (name, res_model, res_id, file_size, mimetype). Binary file content transfer is limited by OneSuite's storage tier cap (30 GB Freelancer, 60 GB Growing Agency); we pre-scan total file volume and flag any account at or exceeding its tier limit. In those cases we migrate document URLs and metadata only, deferring binary transfer to a post-migration file hosting step.

OneSuite Files attached to Projects, Tasks, or Invoices migrate as ir.attachment metadata records. We map the file URL, name, and type but do not stream binary content if the account is approaching its storage cap. File metadata is preserved so that the admin can reattach files from OneSuite's export archive after migration if binary content was deferred.

OneSuite Members map to Odoo res.users records. We resolve Members by email address match. Any Member without a matching Odoo user is held in a reconciliation queue for the admin to provision before record import resumes. Member assignments to Projects, Clients, and Invoices migrate as Odoo's follower mechanism (mail.followers) on the relevant record.

OneSuite's user-defined pipeline stages migrate to Odoo crm.stage records with the same name and sequence order. Stages with custom automation rules (auto-assignment, scoring triggers) are flagged for manual reconfiguration in Odoo Studio. The probability percentage on each stage migrates as a custom float field if the customer's Odoo version uses the older probability model, or is omitted if the customer uses the new Odoo 17+ stage probability approach.

OneSuite Project templates migrate as Odoo project.project records with the is_template flag set to True. Template field structure and default values transfer; template automation logic (auto-assignment on creation, milestone triggers) cannot be replicated automatically and is flagged in the handoff document for Odoo Studio rebuild.

OneSuite Document templates migrate as Odoo report template metadata (ir.actions.report) if the customer uses Odoo Studio's document template builder. We transfer template field structure and conditional logic as a written specification for the admin to reconstruct in Odoo Studio, because template rendering logic is not migratable as data.

OneSuite's custom fields are flattened directly onto entities with their original slug as the property key (e.g., a field named client-tier appears as clientTier on the Client record). We parse each slug, remap it to the equivalent Odoo field name, and pre-create the custom field definition in Odoo Studio before migration runs. Fields that do not have a matching Odoo type are flagged for the admin to configure as selection fields or relational fields. This step is required before any record import to ensure custom field values are not dropped.