Migrate from Paradym to Odoo CRM

Paradigm credential holders map 1:1 to Odoo res.partner records. The is_company flag is set to False for individual credential holders; organizations with nested person attributes are split into separate partner records linked via parent_id. Email, phone, and name fields map directly to Odoo's standard res.partner fields without transformation required.

Credential holders identified as organizations in Paradym map to Odoo res.partner with is_company=True. Their nested person attributes such as authorized contacts and key holders create child res.partner records linked via parent_id. The organizational hierarchy from Paradym translates directly into Odoo's partner contact tree structure.

Paradym top-level attributes (name, email, phone, address components) create Odoo Studio custom fields on res.partner. Field type maps: text strings to char, dates to date, booleans to boolean. We create the custom field in Odoo before migration and map values directly.

Paradym nested attributes under keys like 'person.name' or 'address.city' are flattened into separate Odoo custom fields using dot-notation naming: x_person_name, x_address_city, x_person_firstname, x_address_postal_code. Odoo has no native nested object storage, so grouping semantics are preserved as naming conventions to maintain semantic clarity for Odoo administrators reviewing migrated data.

Paradym array attributes such as multiple nationalities or credential type lists cannot map to a single Odoo field without losing item-level granularity. We split each array item into a child res.partner record with a type tag, or store as a comma-separated custom field — your admin chooses the preferred representation during the pre-migration audit.

Paradym credential presentations — where a holder presents credentials to a verifier — translate to Odoo crm.lead records representing opportunities in the sales pipeline. The presentation date becomes the opportunity create_date, and the presentation outcome (accepted, rejected, pending) maps to crm.lead.stage_id through the pre-configured stage mapping. Each presentation links to the holder's migrated res.partner via partner_id.

Paradym credential templates define attribute schemas and issuance rules controlling credential lifecycle states. Odoo has no direct equivalent template system — we preserve template definitions as exported JSON stored in Odoo's document storage (ir_attachment) for manual reference when rebuilding credential-related custom fields and automated actions in Odoo Studio.

Paradym credential states (Issued, Revoked, Expired, Pending Verification) map to Odoo CRM pipeline stages via value-by-value mapping defined in the pre-migration checklist. We create crm.stage records matching Paradym states before migration begins and route each crm.lead to its corresponding stage based on the source credential status during the migration run.

Paradym verification events — timestamps when a verifier checks a credential — become Odoo crm.activity records linked to the corresponding crm.lead via res_id and res_model fields. Activity type (call, email, meeting), activity date, and verifying user are preserved from the Paradym event for complete audit trail continuity in the Odoo migration target.

Paradym credential documents including PDF certificates and verification screenshots are downloaded via the Paradym API and re-uploaded to Odoo as ir.attachment records. Each attachment links to res.partner via res_model='res.partner' and res_id pointing to the holder's migrated partner ID. File size respects Odoo's attachment storage limits with a default maximum of 100MB per file.

Paradym desk owners and API key holders map to Odoo res.users through email address matching as the primary identifier. Unmatched owners are flagged in the pre-migration report — your Odoo admin either creates the missing user account or assigns all orphaned records to a designated fallback owner before the migration batch executes.

Paradym issuance logs recording timestamps and actors who issued credentials have no Odoo CRM equivalent tracking mechanism. We preserve the complete issuance history as structured JSON in an ir_attachment record linked to the credential holder's res.partner, enabling future audit queries against the JSON blob without requiring custom database extensions.