Migrate from Visual Practice to Odoo CRM

Individual contacts map directly to res.partner records. Odoo stores the contact type in the partner's type field ('contact' vs 'invoice' vs 'delivery'). Parent company link stored in commercial_partner_id or parent_id depending on whether the contact is an individual or organization.

Companies map to res.partner records with type='company'. Odoo automatically links child contact partners to this record via parent_id. Website, industry, and employee-count fields migrate to the equivalent Odoo fields. Parent-company hierarchies in Visual Practice map to Odoo's parent_id chain. Additionally, any custom company-level attributes from Visual Practice (such as revenue tier or sector codes) are stored as custom fields on the res.partner record, ensuring data richness is preserved.

Visual Practice leads migrate as crm.lead records with type='lead'. Stage maps to stage_id from Odoo's crm.stage table for the assigned sales team. Lead scores, source information, and medium (phone, web, referral) map to custom fields or standard Odoo columns (source_id, medium_id).

Visual Practice opportunities and deals migrate as crm.lead records with type='opportunity'. The partner_id links to the corresponding res.partner record. Expected revenue maps to Odoo's planned_revenue field; closed revenue maps to 'Won' stage with date_closed timestamp. Any custom deal attributes (e.g., discount tier, product category, renewal flag) are preserved as custom fields on the crm.lead record, maintaining context for future pipeline analysis.

Visual Practice pipelines do not map 1:1 to a single Odoo object. Each pipeline becomes an Odoo crm.team with its own crm.stage sequence. Teams with multiple pipelines in Visual Practice require multiple crm.team records in Odoo — each with a distinct stage configuration.

Stage names map value-by-value to Odoo's crm.stage records, ordered per team. Probability values attached to each stage in Visual Practice are stored as custom fields in Odoo since probability is computed dynamically in Odoo from historical win rates. Stage-entered timestamps are preserved as a custom datetime field.

Visual Practice custom contact properties require definition as custom fields on res.partner in Odoo — typically via an XML data file in a custom module. Field type (char, selection, float, date) maps to the corresponding Odoo field definition. FlitStack delivers the field definitions alongside the migration so they exist before data lands.

Deal-level custom fields from Visual Practice (discount tier, product category, renewal flag) require definition as custom fields on crm.lead. Type-aware mapping preserves pick-list values as Odoo selection fields and numeric fields as float or monetary depending on the source type.

Logged calls and emails from Visual Practice become mail.activity records attached to res.partner or crm.lead. Meetings map to mail.activity with activity_type_id set to 'Meeting'. Original timestamps, owners (user_id), and subject lines are preserved. Odoo's chatter widget surfaces these on the partner or lead form.

Visual Practice notes migrate as mail.message records with subtype='mt_note', keeping body text, create date, and author preserved. Notes attached to specific records are linked via res_model and res_id references so they appear in Odoo's chatter thread. If Visual Practice notes include tags or categories, these are stored as a custom many2many field on the mail.message record to preserve categorization.

File attachments from Visual Practice re-upload to Odoo's ir.attachment table with the correct res_model and res_id linking them to the parent partner or lead. Odoo's attachment storage (database or filestore) is configurable — we match the destination's current storage setting.

Visual Practice owner IDs resolve by email match against Odoo's res.users table. Unmatched owners are flagged before migration; records can be assigned to a fallback Odoo user or held for manual assignment. This prevents orphaned crm.lead records with no user_id in Odoo.

Visual Practice contact or deal tags map to Odoo's crm.tag model. Tags are many2many fields on crm.lead. If tag names conflict with existing Odoo tags, FlitStack merges or renames them based on a deduplication rule agreed upon before migration. The resulting tag set is applied to all relevant crm.lead records, ensuring that pipeline reporting and segmentation remain accurate after migration.