Migrate from Sunbase Data to Odoo CRM

Sunbase Contact records map to Odoo res.partner with company_type = 'person'. Standard fields (name, email, phone, street, city, state, zip) migrate directly. Sunbase's industry-specific contact fields (financing status, site address, aerial measurement reference) require Odoo custom fields created in Odoo Studio before migration. Contacts export from Sunbase's CRM module separately from Deals; we match by Sunbase contact_id during the import phase so the Odoo partner_id on any linked Deal resolves at insert time.

Sunbase Leads (from door-to-door capture, web forms, and manual entry) map to Odoo crm.lead with type = 'lead'. Lead source and status fields from Sunbase map to Odoo's source_id and stage_id. Sunbase lead assignment data (assigned employee) maps to Odoo's user_id. Any Sunbase lead fields tied to automation workflows are migrated as data only; the automation logic does not transfer and requires rebuild in Odoo Studio.

Sunbase Deals map to Odoo crm.lead with type = 'opportunity'. Deal value (currency amount), pipeline stage, and stage history migrate to Odoo's expected_revenue, stage_id, and stage history log. Custom deal fields (permit tracking flags, proposal version, financing approval status) require Odoo custom fields created before migration. Deals without an associated Sunbase Contact are loaded first; Deals with contacts are loaded after Contact migration to satisfy the partner_id lookup.

Sunbase pipeline stage names and deal statuses are migrated as Odoo crm.stage records within the relevant crm.team. Stage probabilities are set on each stage record. The visual pipeline board itself is not transferable; we document the stage names, ordering, and probability assumptions in a stage-mapping spreadsheet for the customer's Odoo admin to configure in Odoo Studio after migration.

Sunbase Projects (installation or job-site operations) map to Odoo project.project with the Project app installed. Project metadata (name, site address, customer link, status, budget) migrates directly. Sunbase project-specific fields (aerial measurement data, permit tracking, system specifications) map to project.project custom fields. Projects with linked Work Orders are migrated first so that the project_id lookup on Work Order records resolves at insert time. If the customer does not install the Odoo Project app, Projects are migrated as crm.lead custom fields with a note explaining the constraint.

Sunbase Work Orders map to Odoo project.task with the Project app installed. Task fields (name, description, permit info, system specifications) migrate directly. Linked employee assignments from Sunbase map to project.task user_ids (multi-assignee). Scheduling data (start date, due date) migrates to project.task date_start and date_deadline. Attachments on Work Orders migrate as ir.attachment records linked to the parent task. If the Project app is not installed at the destination, Work Orders are not migratable in standard Odoo CRM alone.

Sunbase Invoices map to Odoo account.move with move_type = 'out_invoice'. Invoice line items, payment status, and linkage to the originating project or client migrate to Odoo's account.move.line records. The Accounting app must be installed at the destination for invoice migration to succeed. Historical paid invoices are migrated with state = 'posted' and date set to the original invoice date. Draft invoices are migrated with state = 'draft'. Recurring financing-related invoices require Odoo recurring entry configuration post-migration.

Sunbase Employee records (HR data, crew assignments, role information) map to Odoo hr.employee. Employee metadata (name, department, job title, hire date) migrates directly. GPS location history is not migratable as structured Odoo data; it is exported as a CSV and archived for the customer's reference. The HR app must be installed at the destination. Crew assignment linking (which employee is on which job) maps to project.task user_ids multi-assignee, which requires the Project app as well.

Sunbase Appointments (customer-linked scheduling synced with Google Calendar) map to Odoo calendar.event. Appointment date, time, duration, and linked contact migrate directly. The Odoo Calendar app must be installed at the destination. Google Calendar linkage is not transferable; appointments land as Odoo-native calendar events and must be re-linked to Google Calendar by the customer's admin post-migration using Odoo's Google Calendar synchronization app.

Sunbase Documents (contracts, financing applications, permits, and other files stored within the platform) migrate as Odoo ir.attachment records. File binary content, file name, and upload date transfer directly. The attachment relationship to the parent record (Contact, Deal, Project, Work Order) is preserved via the res_model and res_id fields on ir.attachment. Large binary files are chunked for upload via Odoo's XML-RPC file endpoint.

Sunbase custom objects within its module system have no documented API or export schema and cannot be programmatically migrated. We coordinate with the customer during discovery to identify custom object records stored in Sunbase's database, export them manually, and recreate them as Odoo custom models via Odoo Studio or Python model definition before importing the data. The customer must provide the custom field manifest during scoping because Sunbase does not export field definition metadata.

Sunbase Owner records (assigned sales reps, project managers) map to Odoo res.users by email match. We extract every distinct Owner referenced on Contact, Lead, Deal, Project, and Work Order records. Any Sunbase Owner without a matching Odoo res.users email is held in a reconciliation queue for the customer's admin to provision the corresponding User before record import resumes. Inactive Sunbase owners map to Odoo res.users with active = False unless instructed otherwise.