Migrate from Virtual Case Management to Odoo CRM

Each VCM Case becomes an Odoo crm.lead record. The lead's name field is populated with the client name plus case ID for traceability. The lead's partner_id is set by resolving the client record. Stage is assigned based on the VCM case status mapping.

VCM case statuses are mapped by value. 'Closed - Resolved' maps to Odoo Won stage. 'Closed - Incomplete' or 'Terminated' maps to Lost stage. Cases without a close date remain as open leads in Odoo. FlitStack AI generates the value-mapping table before migration.

VCM Client records map directly to Odoo res.partner. The partner is created with type='contact'. FlitStack AI resolves duplicate partners by email — if a partner with the same email already exists, the case is linked to that record rather than creating a duplicate.

VCM organizations are identified by a flag or org_name field in the source export. These records create Odoo res.partner entries with type='company'. Individual client contacts are created as separate res.partner records with type='contact' and linked to the organization via parent_id. This parent‑child hierarchy is required for Odoo's address book and for proper activity attribution across the CRM.

VCM case plans define service types, deliverables, and deadlines. Odoo has no native case plan object, so FlitStack creates a custom char field x_case_plan on crm.lead to store the plan name. For migrations with multiple plan types, a custom selection field is used instead.

VCM case status values (New, Active, Pending, Closed) map to Odoo crm.stage records. FlitStack AI creates or reuses Odoo stage records matching the source values. Stage display names are matched case-by-case; probability is inherited from the Odoo stage defaults unless custom probabilities are provided.

VCM case_worker_id is a string or user reference. FlitStack AI resolves it to an Odoo res.users record by matching the case worker's email address against Odoo logins. If no match is found, the lead is assigned to a designated fallback user and flagged for admin review before the migration commits.

VCM referral source is stored as a text or pick-list field on the Case record. Odoo CRM has no native referral source field. FlitStack AI creates a custom char or selection field x_referral_source on crm.lead and maps values directly from the source pick-list.

VCM intake_date values are mapped directly to Odoo's crm.lead.date_open field, which powers dashboards and reports that calculate time‑to‑first‑contact and lead aging metrics. If the source VCM record lacks an intake date, FlitStack AI leaves date_open blank and falls back to the lead's create_date, ensuring that pipeline analytics remain accurate even when source timestamps are missing.

VCM case_close_date maps to Odoo crm.lead.date_closed. This field is set automatically by Odoo when the stage is moved to Won or Lost. For migrations where the VCM close date exists but Odoo's stage is not yet Won/Lost, the date is stored in a custom field x_original_close_date for audit purposes.

VCM priority levels (High, Medium, Low) map to a custom selection field x_priority on crm.lead with the same values. Odoo's native priority field is used for CRM-level urgency; the VCM priority is preserved in the custom field to avoid overwriting it during re-imports.

VCM case notes are imported as Odoo mail.message records attached to the crm.lead. Each message records the original author (case_worker), creation date, and body content. Notes are imported in chronological order. Odoo's chatter widget displays them below the lead record.

VCM file attachments are downloaded and re-uploaded to Odoo as ir.attachment records linked to the crm.lead. FlitStack AI preserves the original filename, MIME type, and binary content. Files exceeding Odoo's default 25MB per-file limit are split and linked to multiple records if necessary.

VCM workflow rules, escalation triggers, and deadline reminders have no Odoo CRM equivalent at the schema level. FlitStack AI does not migrate them. We export the rule definitions as a JSON specification document that your Odoo administrator can use to rebuild equivalent rules in Odoo's Automation menu or via Studio.

VCM agency staff records contain login credentials, role assignments, and security tier data that do not map to Odoo's res.users schema. FlitStack AI does not migrate user accounts. Your Odoo administrator creates res.users accounts independently before migration, and FlitStack resolves case worker references against those accounts.

VCM service directory entries are organizational metadata, not client data. They do not map to any Odoo CRM object. If your Odoo deployment includes Odoo Contacts or a custom service catalog, this data can be migrated separately as a custom import job. FlitStack AI can extend the migration plan to include it.

VCM case type defines the category of service being delivered. Odoo CRM has no native case type field. FlitStack AI creates a custom selection field x_case_type on crm.lead with the source pick-list values mapped 1:1. If VCM uses free-text case type, the field is created as a char field.

VCM multi‑agency sharing rules and confidentiality tiers have no direct counterpart in Odoo CRM's standard security model, so FlitStack AI does not migrate them. After migration the Odoo administrator must define record rules on crm.lead and res.partner, assign agency‑specific sales teams, and optionally add a custom agency field to enforce visibility restrictions. FlitStack AI includes a recommended rule set in the deliverables package to simplify this configuration.