Migrate from Filevine to Odoo CRM

Filevine People records map directly to Odoo res.partner. The company_id field links each contact to its parent Organization (also a res.partner record with company_type='company'). Custom contact fields require Odoo custom field creation via Settings > Technical > Models before migration.

Filevine Organizations map to Odoo res.partner records with company_type set to 'company'. All address components including street, city, state, zip, and country map to corresponding res.partner address fields. The website domain from Filevine maps to res.partner.website. Child People records created under the organization link to their parent via the parent_id field on res.partner, preserving the hierarchical relationship. Organizations must be migrated before their associated People records to ensure the parent link resolves correctly during import.

Filevine Projects are the primary migration object. Each project maps to an Odoo crm.lead record. The project name becomes crm.lead.name. Project status (Active, Pending, Closed) informs the Odoo stage mapping. Open projects map to an Odoo pipeline stage of your choosing; closed projects map to a Won or Lost stage.

Each unique Phase name in Filevine becomes a crm.stage value within a specific Odoo pipeline. We create a stage per unique phase name across all project templates so all projects map to their corresponding stage. Stage probability is assigned based on Odoo's default or your custom values. Phase order (sequence) is preserved as stage sequence.

Filevine Deadline Chains define a sequence of dates relative to a trigger date. We translate each chain item into an Odoo planned crm.activity record (type, date_due, user_id) with the chain name and sequence position preserved as custom fields on the activity. The relative-day offset is converted to an absolute date based on the trigger date in Filevine.

Filevine Tasks map to Odoo crm.activity records with activity_type_id set to the appropriate type (call, email, meeting, upload, etc.). Task subject becomes activity summary. Due date maps to date_due. Assigned user maps to user_id via email resolution. Completed tasks map as activity records with state='done' and date_done preserved.

Filevine notes attached to a project migrate as Odoo mail.message records on the crm.lead (using Odoo's messaging system). Rich-text formatting is preserved where possible. If the note contains a file attachment, the file migrates as an ir.attachment linked to the same crm.lead record.

Filevine file attachments migrate as Odoo ir.attachment records. Each attachment is linked to its parent crm.lead record via res_model='crm.lead' and res_id set to the lead ID. Original file names and MIME types are preserved. File size limits: Odoo Community defaults to 25MB per file; larger files are chunked or linked by URL reference.

Filevine custom fields per project section have no Odoo CRM native equivalent. We produce a custom field definition list (field name, type, options, section context) that your Odoo administrator creates via Settings > Technical > Models before migration. Values migrate to those custom fields on crm.lead. Selection-type custom fields require explicit value-by-value mapping since Odoo selection options must be defined at the field level.

Filevine billing items (time entries, expenses, flat fee items) have no Odoo CRM native equivalent. Time entries and expenses migrate as custom number fields on crm.lead capturing total hours and total expenses. If you use Odoo Accounting, billing items can be migrated as account.move lines linked to the partner — this requires the Odoo Accounting module to be installed and adds configuration scope.

Filevine calendar events and depositions map to Odoo calendar.event records. Start datetime, stop datetime, name, and attendees (linked contacts via email) are preserved. Deposition-specific fields (court reporter, Zoom link) migrate as custom fields on the calendar.event if created in Odoo. Odoo calendar syncs with Google Calendar and CalDAV.

Filevine user IDs are resolved against Odoo res.users records by email address. Unmatched owners are flagged before migration. You can either create the Odoo user first or assign their Filevine records to a fallback owner during migration. Active/inactive status is preserved from Filevine.