Migrate from Successware to Odoo CRM

Successware clients map directly to Odoo res.partner records. The customer_rank field (computed from type) is set to 1 for all migrated clients. Primary address data maps to partner address fields; additional addresses require separate res.partner records with address_type='other'. Contact custom fields defined in Successware are created as custom fields on res.partner via the Odoo Studio interface before migration begins.

Successware prospects without closed jobs migrate as Odoo crm.lead with type='lead'. Prospect contact details populate email_from, phone, and street fields on the lead. If the prospect has open or won jobs, we create a res.partner and link it to an opportunity instead.

Successware vendors map to res.partner with supplier_rank set to a value greater than zero (typically 10). Vendor contact information populates the same fields as clients. Odoo distinguishes vendors from customers via separate menu views and the supplier_rank flag, not a separate object. Vendor records become accessible through the Purchasing application in Odoo after migration.

Each Successware job becomes an Odoo crm.lead record with type='opportunity'. The job name maps to crm.lead.name, the scheduled completion date maps to date_deadline, and the job amount maps to planned_revenue. The linked customer resolves to the crm.lead's partner_id through email match against migrated res.partner records. Job type and equipment details become custom fields on the opportunity record.

Successware job statuses (Open, Scheduled, In Progress, Completed, Closed Won, Closed Lost) map to Odoo crm.stage records. We create custom stages matching Successware's workflow if Odoo's default Pipeline Demo stages don't align. Stage-entered timestamps are preserved as custom datetime fields.

Successware Quick Entry invoices migrate to Odoo account.move with move_type='out_invoice'. Invoice number becomes name, invoice date maps to invoice_date, and total amount maps to amount_total. The invoice state (Draft, Posted, Cancelled) maps directly to Odoo's state field. A custom boolean field x_quick_entry flags the original type.

Cost Plus invoices migrate to account.move with move_type='out_invoice', but the Cost Plus markup percentage and cost-basis fields have no Odoo native equivalent. We create custom fields x_cost_plus_markup_pct (float) and x_cost_basis (monetary) on account.move to preserve this data. These fields allow the finance team to review margin calculations after migration without relying on external spreadsheets.

Successware equipment records containing serial number, make, model, install date, and service history have no direct Odoo CRM equivalent. We create custom fields on crm.lead: x_equipment_serial (Char), x_equipment_make (Char), x_equipment_model (Char), x_equipment_install_date (date). Service history lines become a custom one2many relation x_equipment_service_ids. The equipment fields are created via field creation script before migration loads begin.

Successware employee records map to Odoo res.users for owner resolution on migrated crm.lead records. Employee email becomes res.users login; employee name becomes res.users name. Employee role and department become custom Char fields x_employee_role and x_department on the user record. Unmatched employees are flagged in the pre-migration audit report for admin review before migration execution.

Successware PriceBook items map to Odoo product.product with type='service'. Item code maps to default_code, description maps to name, and unit price maps to list_price. Active or inactive status maps directly to the active boolean. Standard versus custom pricing flags require a custom selection field (x_pricing_type) since Odoo does not distinguish these categories natively.

The Successware A/R Aging Report exported as XLSX contains unpaid balance amounts and aging buckets (current, 30 days, 60 days, 90+ days). These map to custom monetary fields on res.partner: x_ar_current, x_ar_30_days, x_ar_60_days, x_ar_90_plus_days. Matching invoice line records in account.move.line also receive aging bucket fields for reconciliation accuracy.

Successware custom fields on contacts beyond standard name/email/phone require Odoo custom field creation via Settings > Technical > Database Structure > Models. Fields are added to res.partner with appropriate data types (char, selection, float). We deliver a field creation script as part of the migration plan, which your Odoo admin applies before data loads commence.