Migrate from Powered Now to Odoo CRM

Powered Now clients map directly to Odoo res.partner records typed as 'company'. The partner's name field holds the business name. Its address fields (street, city, postcode) map to Odoo's street, city, and zip fields. Contacts under the client in Powered Now become res.partner address records (type='contact') linked to the company partner via parent_id.

Powered Now contacts under a client become Odoo contact addresses on the parent res.partner record. The name, email, and phone fields map directly. If the same person appears under multiple Powered Now clients, Odoo's parent_id resolves the primary company; secondary associations can be noted in a custom multi-company field or left as address records for reference.

Each Powered Now job becomes a crm.lead record in Odoo CRM. The job name maps to crm.lead.name, the job description maps to crm.lead.description, and the client (business name) populates crm.lead.partner_id via lookup on the previously migrated res.partner. The original Powered Now job status is preserved in a custom field job_status__c.

Powered Now's freeform job status values (e.g. 'Quoted', 'Scheduled', 'In Progress', 'Complete') have no native Odoo equivalent since Odoo uses pipeline stage names. A custom char or selection field (job_status__c) is created on crm.lead before migration. Stage-based filtering in Odoo's Kanban view uses the standard stage_id field; job_status__c stores the original label for historical reporting.

Powered Now quotes map to Odoo sale.order records in 'draft' or 'sent' state depending on their status in Powered Now. The quotation name, line items, quantities, and unit prices migrate as sale.order.line records. The linked job's crm.lead ID is stored in a custom field sale_order__c for traceability. Existing accepted quotes can be confirmed to sale orders during migration.

Powered Now invoices migrate as account.move records of type 'out_invoice'. The invoice number maps to account.move.ref, the client to partner_id, and line items to invoice_line_ids. Odoo's account.move has a much richer tax and reconciliation model — taxes are mapped by name match to Odoo's account.tax records, and payment state is set based on whether the invoice was paid in Powered Now.

Compliance certificates (gas safety, electrical test, etc.) from Powered Now migrate as ir.attachment records attached to the related crm.lead or res.partner. The original filename and MIME type are preserved. Expiry dates for certificates are stored in a custom date field certificate_expiry__c on the attachment's related record so renewal reminders can be configured in Odoo.

Powered Now team members and assigned engineers are matched to Odoo res.users records by email address. Unmatched users are flagged before migration — the team either creates Odoo user accounts first or assigns records to a fallback user. The user's name and email map directly; their role in Powered Now (e.g. 'Gas Engineer') can be stored as a custom field on res.users.

If Powered Now supplier invoices or purchase orders are in scope, they migrate as Odoo account.move records of type 'in_invoice' or purchase.order records. The supplier company maps to res.partner (type='supplier'), and line items map with supplier product references where available.

Any custom fields defined in Powered Now on jobs (e.g. 'Boiler Make', 'Flue Type', 'UPRN') are created as custom fields on crm.lead in Odoo before migration using Odoo Studio or a custom module. Field types are inferred from Powered Now's field definitions — text fields become char, selection lists become selection, numeric values become float or integer.

Text notes attached to jobs migrate as ir.attachment records linked to the crm.lead. Large text notes may also be appended to the crm.lead.description field. File attachments (photos, PDFs) re-upload to Odoo's filestore as ir.attachment records. The original create date is preserved in the attachment's create_date field.

Powered Now's diary entries and scheduling blocks have no direct Odoo CRM equivalent — Odoo's calendar.app manages meetings and events separately from CRM. We preserve the scheduled date and assigned user from Powered Now diary entries as custom datetime fields on crm.lead (scheduled_date__c, scheduled_user__c). Calendar events must be rebuilt in Odoo's calendar.app using those values as reference.