Migrate from PBS Systems to Odoo CRM

Assess PBS data export capability and inventory all objects

FlitStack reviews your PBS contract to confirm access to the PBS Database Export Interface or identifies the most direct export path (CSV via PBS reporting module, direct database query if available). We inventory all PBS objects — contacts, companies, deals, vehicles, parts, service write-ups, and activity logs — and count records per object. This assessment phase produces the Migration Scope Document that drives the fixed-price quote and identifies any objects that require custom Odoo field creation before migration.

Define Odoo schema: custom vehicle model, F&I fields, repair history model

Before data moves, FlitStack creates the Odoo field definitions needed to receive PBS automotive data. This includes: the custom.vehicle model with all vehicle attribute fields and the partner_vehicle_rel many-to-many table, custom fields on crm.lead for F&I products (GAP, ESC, tire-and-wheel, lender name, RouteOne reference), and the custom repair_history model for service write-up records. We deliver a schema setup plan so your Odoo admin can create the fields and models in a staging environment before the migration run.

Map all fields and extract PBS data in dependency order

We build the complete field mapping document covering every PBS source field to every Odoo destination field, including value-mapping tables for state names, industry names, lead status, and deal stage. Contacts and companies export first (they have no dependencies), then vehicles, then deals with their F&I fields, then activities. The PBS export runs in staging against a sample period to validate field coverage before the full extraction commits. Any missing fields or PBS data quality issues surface here.

Run sample migration with field-level diff and owner resolution

A representative sample — typically 100–500 records spanning contacts, companies, deals, vehicles, and activities — migrates into Odoo staging. We generate a field-level diff report showing source value, mapped destination value, and any transformation applied for every field. Owner resolution runs: PBS owner IDs matched by email against Odoo res.users; unmatched owners flagged for your team to either invite to Odoo or assign to a fallback user. You review the diff report and approve or adjust the mapping before the full run proceeds.

Execute full migration with delta-pickup window and audit log

The full PBS dataset loads into Odoo. A delta-pickup window — typically 24–48 hours — captures any records created or modified in PBS during the cutover period. Every migration operation is written to an audit log with source record ID, destination record ID, field count, and timestamp. One-click rollback reverts all destination changes if reconciliation fails. After rollback is confirmed, a final validation pass checks record counts, field population rates, and owner resolution coverage against the pre-migration scope document.

Deliver migration artifact package and rebuild reference documentation

FlitStack delivers the complete artifact package: Odoo data import files, field mapping spreadsheet, Odoo Studio export of custom fields and models created, and the audit log. We also deliver a Workflow Rebuild Reference document that walks through each PBS workflow, automation, F&I product rule, and RouteOne configuration so your Odoo admin can reconstruct them using Odoo Studio automations or a custom module. PBS contracts with PBS support for any workflow-related questions during the rebuild phase.