Migrate from Formaloo to Odoo CRM

Formaloo Forms have no direct Odoo CRM equivalent. During scoping we analyze each Form's field structure to determine whether it represents customer records (map to Lead or Contact), transactional records (map to Opportunity or custom fields on Account), or reference data (map to custom selection fields). Forms used as contact intake — with fields for name, email, phone, company — map to Odoo Lead fields. Forms with only a handful of structured fields that describe a business entity map to Contact fields with the Form name stored as a tag. We create an inventory of all Forms ranked by data volume and record-type fit before any mapping decisions are finalized.

Each Form Response row maps to one Odoo CRM record. We extract the response data via Formaloo's Excel export or REST API, transform each field by type: text fields map to Odoo char or text fields; email fields map to email; phone fields map to phone; date fields map to date; rating fields map to integer or selection; choice fields map to selection or many2one depending on whether the choice list corresponds to an existing Odoo model. The Form submission timestamp maps to lead_date or lead_create_date as a custom field. Response rows with no matching Odoo user (the Form respondent) map to an Odoo Lead rather than a Contact.

Each Formaloo field type maps to a corresponding Odoo field definition. Calculation fields (Formaloo's computed expression fields) become Odoo float or monetary fields storing the computed value as a static number — the live formula does not carry over. Signature fields (available on paid Formaloo plans) become ir.attachment records linked to the parent Lead or Contact via a many2one relationship. File upload fields become ir.attachment records. We create Odoo custom fields via the Settings > Technical > Custom Fields interface or by direct xml data import before any records are migrated.

Formaloo Relational Databases link multiple Forms via reference fields. If a Database contains a Form A with a reference field pointing to Form B records, we treat Form A as the parent record and Form B records as the referenced entity. The reference field maps to an Odoo many2one custom field pointing to the mapped Odoo object (res.partner or crm.lead). We run a lookup resolution step that reads the Formaloo reference field values, matches them to the corresponding Odoo record IDs created in the prior migration phase, and injects the resolved many2one ID during the import. Many-to-many cross-references map to Odoo many2many fields with an intermediate link table.

Formaloo Workspaces act as organizational containers for Forms and Databases. We map Workspace membership to Odoo CRM Tags on the migrated Lead or Contact records. A tag naming convention using workspace-form-slug keeps the organizational layer recoverable. If the customer uses Workspace-level permissions that map to Odoo Teams or Sales Teams, we create corresponding Odoo crm.team records and assign the migrated leads to the appropriate team via the team_id field during import.

Formaloo Folders provide a nested file-organization layer within Workspaces. We capture folder paths as tag prefixes (e.g., sales-inbound-lead-questions or finance-b2b-inquiry) on the Form Response records. The folder hierarchy is preserved in a custom description field as a breadcrumb string (e.g., Sales Pipeline / Inbound / Q4 2024) for cases where the customer needs full path reconstruction.

Formaloo conditional logic, field visibility rules, and calculation formulas are UI-defined automation that does not export as structured data. We do not migrate Logic Rules. We produce a written Logic Rule inventory — one entry per Form — that documents each rule's trigger condition (e.g., if field X equals Y, then show fields A, B, C), the affected fields, and a recommended Odoo Studio equivalent or Python compute method. The customer's Odoo admin uses this inventory to rebuild the conditional logic post-migration.

Formaloo integrations (Google Sheets two-way sync, Wix, Pabbly, webhooks) are Formaloo-specific connection configurations that do not transfer to Odoo CRM. We document each active integration, its trigger, its destination, and the webhook payload structure so the customer's Odoo admin can recreate equivalent automations using Odoo Webhooks, Odoo Studio, or an iPaaS connector. The Google Sheets integration is the most commonly requested replacement — we recommend Odoo's native spreadsheet module or the Google Drive integration.

Formaloo folder-level access management maps to Odoo user access rights. We export the Formaloo permission matrix (which users have access to which Forms and Workspaces) and map it to Odoo User records and CRM Team membership. Folder-level Formaloo permissions that restrict specific Forms do not map directly to Odoo's permission model — we document the gap and recommend Odoo Record Rules as the equivalent control, which the customer's Odoo admin implements post-migration.

Formaloo Form and app templates are copyable structural artifacts without customer data. They do not migrate as they are a configuration feature of the source platform, not customer records. We recommend the customer uses Odoo's template functionality in the destination to recreate the most-used form structures as Odoo Lead templates or quick-create forms.

Formaloo records a submitted_at timestamp on each Form Response. We map this to a custom field (e.g., original_submission_date) on the Odoo Lead or Contact record, preserving the original submission date for historical record-keeping. Form Response edit timestamps map to the lead's write_date if available. Odoo does not preserve audit-style modification history on standard records without additional configuration, so we flag this limitation in the scoping documentation.

Formaloo rating fields (1-5 or 1-10 scale) map to Odoo integer fields with validation constraints. If the rating represents a satisfaction score, we map it to a selection field with labeled options (e.g., Very Unsatisfied, Unsatisfied, Neutral, Satisfied, Very Satisfied) using Odoo's selection field definition. The customer selects the mapping strategy during scoping based on how they used the rating field in Formaloo.