Migrate from Fulcrum Snap to Odoo CRM

Fulcrum Snap clients (SAP business partners) map directly to Odoo res.partner records. The company flag is set on res.partner for entity-level clients and cleared for individual contacts. Address, phone, email, and VAT fields transfer with field-by-field mapping. The original SAP partner number is stored in a custom field for traceability.

Fulcrum Snap contacts associated with a client become Odoo res.partner records with parent_id set to the linked company partner. Contact roles (Billing Contact, Responsible Attorney) map to res.partner categories or a custom contact_role field. Email, phone, and job title transfer directly.

Fulcrum Snap matters are split across two Odoo objects: the crm.lead holds the commercial pipeline stage (New Business Inquiry, Quoted, Engaged), and a project.project record tracks the matter as a project once the engagement is confirmed. Matter number and description map to crm.lead name and description fields.

Fulcrum Snap matter lifecycle stages (New Business, Conflict Check, Engagement Confirmed, Closed) map to Odoo crm.stage records with value-by-value mapping. Probability weights are assigned per stage from Odoo's stage configuration. Custom stages beyond the standard set are recreated as new stage records before migration.

Historical time entries migrate as Odoo analytic line items linked to the corresponding project.project record. Fields mapped include: employee/owner (res.users by email match), date, hours, description, and billing code. Billable/non-billable flags map to Odoo's line-level billable toggle. LEDES billing codes are preserved as tags on analytic lines.

Fulcrum Snap billing records (SAP AR invoices) migrate as Odoo account.move entries of type 'out_invoice' or 'out_refund'. Invoice lines map to account.move.line entries with product, quantity, unit price, and tax. The original SAP invoice number is stored in Odoo's invoice reference field. Payment status is migrated as the move state.

Fulcrum Snap conflicts-check records (party screened, conflict status, screened date, screened by) are summarized as a note or internal note on the associated res.partner record. If a conflict was identified, the note includes the conflict party and resolution. We preserve the full conflict report as an attachment on the partner record.

Fulcrum Snap leads and prospective clients not yet confirmed as matters migrate as Odoo crm.lead records directly. All standard lead fields transfer: name, contact phone, email, company name, and source channel map field-by-field. The responsible attorney assignment resolves to an Odoo res.users record by email lookup. Fulcrum Snap lead status values map to Odoo's crm.stage pick-list entries using value-by-value mapping, preserving the original pipeline position for each prospect record.

Any Fulcrum Snap custom fields on the SAP business partner object are recreated as Odoo ir.model.fields (x_ prefix) on res.partner. Field type is matched: text fields to char/text, pick-lists to selection fields, numeric fields to float or integer. Values are mapped during migration.

Fulcrum Snap custom fields attached to matter records are recreated as custom fields on crm.lead in Odoo. Matter-specific pick-list values require value_mapping — we document each pick-list value pair and apply it during migration. Fields that reference related records (e.g., responsible partner) are resolved to Odoo res.partner or res.users records by email or name match.

Fulcrum Snap workflows (new-business-intake sequences, conflict-triggered holds, approval routing) do not have a native equivalent in Odoo CRM. FlitStack exports the workflow definitions as a structured XML document describing triggers, conditions, and actions. Odoo Studio or a Python developer uses this document to rebuild equivalent automations.

Documents attached to Fulcrum Snap clients and matters are downloaded and re-uploaded to Odoo as ir.attachment records linked to the corresponding res.partner or crm.lead. File size limits (Odoo default 100MB per attachment) are respected. Binary formats and filenames are preserved.