Migrate from Zurple to Odoo CRM

Conversation history has no native Odoo equivalent — it becomes a custom text field

Zurple's Conversations™ feature generates a behavioral email thread stored directly on the contact record — time-triggered, condition-based messages that reflect each lead's engagement withZurple IDX listings. Odoo CRM has no concept of behavior-triggered conversation threads; its activity model (mail.message) logs what happened but not why it was triggered. We preserve the thread content as a long-text custom field on crm.lead so agents can read the full history, but the trigger logic — the conditions that sent each message — must be rebuilt in Odoo's Automation app using the exported sequence definitions. This is not a limitation of the migration tool; it is a fundamental model difference betweenZurple's nurture engine and Odoo's activity model.

IDX referral metadata requires custom field creation before data lands

Zurple's IDX website integration captures which MLS listing a lead viewed, the search URL, the search criteria that generated the lead, and whether the lead originated from aZurple-hosted landing page. Odoo captures UTM parameters natively and stores them on crm.lead, but there is no native field for IDX listing ID, IDX search URL, or the specific property type a lead was browsing. These must be created as custom fields (idx_listing_id__c, idx_search_url__c, lead_origin_page__c) in the Odoo CRM database before migration data is written. If the schema setup step is skipped, this metadata is silently dropped because the target fields do not exist. FlitStack creates these fields during the pre-migration schema setup phase, but Odoo admin credentials with technical write access are required.

Lead-to-opportunity conversion model invertsZurple's pipeline assumptions

Zurple treats every contact in the pipeline as an opportunity — there is no separate lead object. Odoo CRM distinguishes between crm.lead (unqualified) and crm.lead converted to opportunity (qualified). If yourZurple pipeline includes leads that have never been contacted, they land in Odoo as unqualified leads, which means they appear in the Leads kanban view rather than the Opportunities pipeline view. Agents must manually mark them as won or convert them to see them in the main pipeline. This can be disruptive if your team is accustomed to aZurple-style flat pipeline where every record appears regardless of qualification stage. We can pre-qualify allZurple pipeline records as opportunities at migration time by setting the stage_id to a chosen pipeline stage, but this requires a pre-migration decision on whichZurple stages should map to qualified opportunities.

Odoo Community vs. Enterprise determines whether custom field creation requires developer access

If your Odoo instance is Community edition, creating custom fields on crm.lead requires either developer mode enabled (Settings > Activate Developer Mode) or a module development environment to register the field in the ORM. In Odoo Enterprise, the Studio app allows field creation through the UI. If you are running Odoo Community without developer mode, FlitStack's schema setup step may require your Odoo administrator to enable technical features or to install a small scaffolding module that registers the custom fields. This is a pre-migration configuration step that must be completed before the data migration begins — it cannot be done retroactively without a database migration of its own.

MLS saved listings are metadata only — MLS feed reconnection is a separate integration step

Zurple's MLS integration stores saved listing references (listing ID, address, price, status) linked to contacts. These references migrate to Odoo as custom fields on crm.lead, and any listing PDFs attached toZurple contacts migrate as Odoo attachments. However, the actual MLS data feed — the live connection that pulls current listing availability, price changes, and status updates — is not part of the migration scope. Once Odoo CRM is live, MLS reconnection requires either an Odoo MLS connector app from the Odoo App Store or a custom integration with your MLS provider's API. FlitStack documents the MLS field names we created and maps them to the data you need to re-populate, but the live feed itself must be re-established post-migration.