Migrate from Formitize to Odoo CRM

Formitize Clients map directly to Odoo res.partner records with partner_type set to 'company'. Client name, address, phone, email, website, and industry fields map to their Odoo equivalents. Custom fields on the Client object become x_fieldname custom fields on res.partner. The Formitize client_id is preserved as x_formitize_client_id for traceability, and the original create_date is stored as x_original_create_date for historical continuity in Odoo reporting.

Formitize Contacts map to res.partner with partner_type='contact'. The parent_id field links each Contact to the Odoo res.partner record representing the Contact's parent Client, preserving the account hierarchy. Formitize contact-level custom fields become x_fieldname custom fields on the partner record. Email, phone, mobile, and job title map directly to their Odoo equivalents. The Formitize contact_id is preserved as x_formitize_contact_id for traceability and delta-run de-duplication.

Formitize Deals in the Sales Pipeline map to Odoo crm.lead records. Deal name becomes crm.lead.name, deal value (amount) maps to crm.lead.planned_revenue, close date maps to crm.lead.date_deadline, and Formitize stage name maps to crm.stage.name (stage creation in Odoo required before import).

Each Formitize pipeline stage requires a pre-created Odoo crm.stage record within the target crm.team. Stage names are matched value-by-value. Stage sequence (stage_number or sequence field) must match Formitize's stage order for correct Kanban display. Probability values on Odoo stages should be set to match Formitize stage probabilities.

Formitize Jobs are a distinct object with no Odoo equivalent. We map Jobs to crm.lead records with a custom field (x_job_origin='formitize') to distinguish them from pipeline Deals. Job type, priority, and location custom fields carry over as Odoo custom fields on crm.lead. If the Project module is active, Jobs with sub-tasks may become project.task records.

Formitize Job statuses (e.g., Quoted, In Progress, Completed, On Hold) are mapped to a separate set of crm.stage records scoped to a dedicated Odoo team for Jobs. This prevents Job stages and Deal stages from mixing in the same pipeline view. Each status name is matched to a pre-created Odoo stage.

Formitize Assets with serializable tracking map to stock.production.lot records in Odoo (linked to a product.product template). Service-only assets with no inventory tracking become product.product records with type='service'. Asset custom fields (zones, location, GPS) map to custom fields on the Odoo model.

Formitize QuoteAccept quotations map to Odoo sale.order records. Quote status (Sent, Accepted, Declined) maps to sale.order.state and state transitions. Line items from the quote become sale.order.line records. This mapping requires the Odoo Sales module to be installed in the target database.

Formitize PayNow payment records map to Odoo account.payment records linked to the corresponding sale.order (if paid against a quote) or account.move (if paid against an invoice). Payment method (Credit Card, Apple Pay, Google Pay) is stored as a custom field or journal_id selection in Odoo.

Formitize file attachments on Jobs, Clients, Contacts, and Deals are exported and re-uploaded as Odoo ir.attachment records. Each attachment is linked to its parent record (res.partner, crm.lead, or project.task) via res_model and res_id. Inline images in notes are downloaded and re-hosted in Odoo's filestore.

Formitize user records are matched to Odoo res.users by email address. Owner ID on Jobs and Deals becomes crm.lead.user_id in Odoo. Users without a matching email are flagged in the pre-migration audit; records can be assigned to a fallback user or held pending Odoo user creation.

Every Formitize custom field requires an Odoo custom field (x_fieldname) created on the target model before migration. Text, number, date, and email types map to corresponding Odoo field types. Picklist fields require Odoo selection values to be pre-created; multi-select fields may require a custom widget or relational field depending on the Odoo version.

Formitize workflow rules have no Odoo equivalent. FlitStack exports the full workflow definition as a JSON file (workflow name, trigger conditions, action sequence, notification rules) for your Odoo admin to reference when rebuilding in Studio. No workflow data is imported into Odoo automatically.

Formitize Zapier integrations connecting to Google Sheets, Slack, Calendly, or Wave cannot be migrated. Each integration must be re-created in Odoo using Odoo's native integrations, webhook modules, or a middleware platform. We provide an inventory of active Zapier zaps as part of the pre-migration audit.

Formitize Location Zones attached to addresses are evaluated for their intended use. If zones are informational labels (e.g., building names, territory tags), they map to a custom Char field (x_location_zone) on res.partner. If zone tracking is operationally significant for warehouse management or field routing, zones become stock.location records in Odoo Inventory, linked to the partner's address for location hierarchy purposes.