Migrate from Summit Service Systems to Odoo CRM

Summit customers map directly to Odoo res.partner records. Summit's separate Company and Site records collapse into one partner record with multiple delivery addresses stored on res.partner as address children. Parent-company relationships in Summit map to Odoo's Parent Partner field on res.partner.

Summit contact records (named individuals linked to a customer) map to the same res.partner model. Odoo treats contacts and companies as the same table — a contact without a company lands as a partner with no parent. Primary-contact flag from Summit becomes a custom boolean field on res.partner.

Work orders with a sales angle (quoted service, upsell opportunity) map to Odoo crm.lead as opportunities. Work orders representing actual field deliverables (scheduled service visits) map to project.task linked to the opportunity. The mapping decision is driven by the work-order type field in Summit.

Summit work-order line items (parts used, labor hours, service fees) merge into Odoo sale.order.line if the work order has a quote, or into account.move.line if it is a post-service invoice. Line-item taxes from Summit map to Odoo's tax tags on the corresponding invoice.

Summit invoices map to Odoo account.move records with move_type='out_invoice'. Original invoice numbers become the Odoo invoice reference. Line items map to account.move.line with account_id resolved from Summit's income-account mapping. Paid status in Summit sets state='posted' in Odoo. Any open or overdue status translates to Odoo's 'not_paid' state, preserving the original due date in a custom field for reconciliation.

Summit service agreements with recurring billing terms map to Odoo sale.subscription. Subscription lines carry the recurring product or service, the recurrence interval (monthly, quarterly, annual), and the auto-invoicing policy. One-time-only service contracts with no recurrence become crm.lead notes or custom fields.

Summit technicians resolve to Odoo res.users by email match. Active technicians in Summit become active Odoo users; inactive or archived technicians become Odoo portal users with read-only access to their assigned work orders. Unmatched technicians are flagged before migration and assigned a default Odoo user.

Summit service reminders (scheduled callback dates, renewal notices) map to Odoo mail.activity records linked to the res.partner or crm.lead. Original reminder date becomes the Odoo activity's date_deadline. Activity type (call, email, meeting) maps to Odoo's activity_type_id. If a reminder includes a specific technician assignment, the activity also records the user_id to preserve the original owner.

Summit inventory items map to Odoo product.product (storable products). Unit of measure from Summit maps to Odoo's uom_id. Part numbers from Summit become the product's default_code. If Summit tracks serial numbers, those migrate to Odoo's stock.production.lot records linked to the product.

Summit file attachments (photos, diagrams, signed forms) re-upload to Odoo ir.attachment linked to the corresponding record (res.partner, crm.lead, or account.move). File size limits from Odoo (typically 25MB per file) apply; large files are flagged before migration. Original filenames are preserved.

Summit internal notes attached to work orders or customers migrate as Odoo mail.message records with message_type='comment'. They retain the original create date and author (resolved by email match to res.users). Chatter messages on the partner or lead form show the full history.

Summit custom fields on customers create Odoo custom fields on res.partner via Odoo Studio or __manifest__ definition. Field types map: Summit text → Odoo char, Summit number → Odoo float or integer, Summit date → Odoo date, Summit pick-list → Odoo selection. Pick-list values require explicit value mapping.