Migrate from Pawa to Odoo CRM

Pawa Contact records (name, phone, email, custom fields) map to Odoo res.partner records with partner_type = contact. Email maps to email field, phone to phone or mobile depending on Pawa field name. We preserve the original Pawa contact ID in a custom field x_pawa_id for reconciliation. Custom fields discovered at scoping time are mapped to equivalent Odoo field types (char, text, selection, boolean, integer, float) before import. If Pawa exposes a company_id on the contact record, we resolve the partner ID from the Company migration phase before writing contacts.

Pawa Company records map to Odoo res.partner with partner_type = company. Company name maps to the partner name field; address fields (street, city, country) map to Odoo's address fields on the partner record. We create company partners first in the migration sequence so that contact records can reference them via the parent_id relationship on res.partner. If Pawa exposes contacts linked to a company, those contacts receive parent_id = the company partner ID in Odoo.

Pawa Deal records (value, stage, linked contacts) map to Odoo crm.lead with type = opportunity. Deal value maps to the expected_revenue field; deal stage maps to stage_id in Odoo CRM. We create the pipeline stages in Odoo during configuration before importing deals so that stage_id references are valid at import time. Linked contacts are resolved by matching Pawa contact ID to the x_pawa_id field we set during the contact migration phase.

Pawa pipeline stages are enumerated at scoping time and mapped to Odoo crm.stage records within the relevant crm.team or pipeline. We preserve stage ordering using the sequence field on crm.stage. If Pawa exposes stage probability values, we set them on the stage records; otherwise we use Odoo CRM defaults. Each stage is created in the Odoo CRM pipeline before any deal records are imported.

Pawa custom fields on Contacts and Companies are discovered via API at scoping time. We create equivalent Odoo custom fields on res.partner using Odoo Studio or direct field creation before migration begins. Field types are mapped: text inputs become char or text depending on length; number inputs become integer or float; checkbox inputs become boolean. Selection fields in Pawa become selection fields in Odoo with the same option labels.

Pawa tag strings stored as arrays on contact and company records map to Odoo res.partner.category records (Tag model). We create the tag records in Odoo during migration, then write the category_id many2many relationship on each partner record. Odoo's tag model supports color coding which can be mapped from any tag metadata in Pawa if available.

Pawa user records (name, email, role) map to Odoo res.users by email match. We extract all distinct owners referenced on Pawa records during scoping and check for matching Odoo users by email. Any Pawa owner without a matching Odoo user is flagged in the migration plan for the customer to provision before migration. Inactive users in Pawa are excluded unless the customer requests otherwise.

Pawa Field Records, which are the offline-collected data entries that are core to Pawa's value proposition, are mapped to Odoo crm.lead records or to a custom Odoo model if the customer has configured one. We evaluate the Field Record schema at scoping and recommend whether they map to Opportunities, to a custom crm.field.record model, or to project.task if they represent work orders. The customer selects the destination model during configuration.

Pawa does not expose file attachments via its documented API. We do not migrate attachments and exclude them from the record count used to scope migration timelines and pricing. Before migration, we provide a list of attachment-bearing records so the customer can manually download files from Pawa and upload them to Odoo using the Documents app or ir.attachment records post-migration.

If Pawa exposes activity timestamps or notes on contact or deal records, we map them to Odoo mail.message records linked to the res.partner or crm.lead via model, res_id, and message_type fields. Note content becomes body field in mail.message; timestamps become date fields. If Pawa does not expose activity data via API, we document this gap in the migration report and note that activity history is not migratable from this source platform.

Pawa user roles are mapped to Odoo access groups (res.groups) during configuration. We read the available roles from Pawa at scoping and create corresponding Odoo groups (Sales Manager, Salesperson, Field User) before user migration. Group membership is assigned based on the role mapping defined during the discovery call. Odoo's default access rights model (Security Administrator, User, Portal) is used as the baseline.

Any third-party integrations connected to Pawa are documented during scoping and flagged as requiring reconfiguration in Odoo. We do not migrate integration credentials or webhook endpoints. The migration deliverable includes a written integration map listing each connected system, the data it syncs, and the recommended Odoo equivalent (native app, Odoo App Store module, or custom integration). The customer reconfigures integrations post-migration.