Migrate from Vaulta to Odoo CRM

Vaulta Contact objects map directly to Odoo CRM crm.lead records with type='lead' when the Vaulta contact is not yet converted. The Vaulta contact's email, name, phone, and address fields translate to crm.lead email_from, contact_name, phone, and street/city/country fields respectively using Odoo's standard field naming conventions. Owner assignments are resolved via email match to res.users.

Vaulta Account objects map to Odoo res.partner records with customer_rank based on account classification. Vaulta account name, industry, website, and employee count translate to res.partner name, industry_id, website, and employee_count fields using Odoo's selection field values for standardized picklists.

Vaulta Study objects do not have a direct Odoo equivalent. FlitStack AI maps Study records to Odoo crm.lead with type='opportunity', using the Study name as opportunity name and Study protocol as description. Study metadata (protocol number, phase, status) is stored in Odoo custom Char fields created during schema setup.

Vaulta Site objects represent clinical or operational sites and map to Odoo res.partner records with a 'is_site' custom flag. Site-specific address and contact information becomes the partner's primary contact record, linked to the parent Account (Vaulta Account) via parent_id on res.partner.

Vaulta Subject records (clinical trial participants) have no Odoo CRM native equivalent. FlitStack creates an x_crm_subject custom model inheriting from crm.lead to store subject ID, site linkage, enrollment date, and subject-specific custom fields from Vaulta. Subjects are linked to Site partners via many2one relationship.

Vaulta Product objects map to Odoo product.template with standard name, description, list_price, and standard_price fields preserved during migration. Vaulta product categories translate to Odoo product.category records with parent_path hierarchy maintained for nested category structures in the target Odoo instance.

Vaulta custom object types (Enterprise feature) require Odoo module creation with new model definition. FlitStack generates an Odoo Python module defining the custom model via _inherit and adds custom fields matching Vaulta's custom field definitions with appropriate ttype translation from Vaulta vType to Odoo field type.

Vaulta documents attached to any Vaulta object (Study, Site, Contact, Account) map to Odoo ir.attachment records. The Vaulta document's name, create_date, create_uid, and content (binary file) are preserved in Odoo's attachment store, with res_model set to the mapped Odoo model and res_id set to the target record ID.

Vaulta cross-object relationships (study_has_sites, account_has_contacts, site_has_subjects) are reconstructed in Odoo using many2one or many2many fields defined in the target model's Python class. Relationships are resolved after all source records are inserted, using source Vaulta record IDs stored in custom migration_id fields for traceability.

Vaulta owner_id on any record maps to Odoo res.users via email match. Unmatched owners are flagged pre-migration. Your team either provisions Odoo users before migration or assigns records to a fallback user (typically admin). Vaulta role and vault-access restrictions do not map to Odoo — those must be reconstructed via Odoo access groups and record rules.

Vaulta custom fields on any standard object require Odoo field creation via Studio or Python module. Vaulta vType (string, number, date, selection, multi-select) translates to Odoo ttype (char, float, datetime, selection, many2many). Custom fields use x_ prefix in Odoo. Required fields and validation rules are flagged for manual setup in Odoo Studio.

Vaulta Study lifecycle states (Draft, Active, On Hold, Closed, Terminated) map to Odoo crm.lead stage_id values. Each Vaulta lifecycle state corresponds to a named stage in the Odoo CRM pipeline, with stage probability values set to match the Odoo team's forecast category configuration.