Migrate from Livespace CRM to Odoo CRM

Livespace Persons map to Odoo CRM Contacts. Standard fields (name, email, phone, address) migrate 1:1. Custom additional fields on the Person record are schema-discovered via the Get custom fields endpoint before transformation, then created as equivalent custom fields on the Odoo res.partner model via Odoo Studio. Lifecycle stage values stored as picklist selections migrate to a custom contact field in Odoo.

Livespace Companies map to Odoo CRM Companies (also res.partner with is_company=True). Company-to-Person associations are preserved as the partner_id link on the Contact record. The Livespace company domain becomes the Website field in Odoo and is used as a dedupe key during import to prevent duplicate company records.

Livespace Deals map to Odoo CRM Opportunities. The Deal's assigned Space determines which Odoo pipeline stage it maps to; if Livespace uses multiple Spaces, we flatten them into a single Odoo pipeline with stage names derived from the most commonly used Space process steps. Deal value, close date, owner, and custom deal fields migrate directly. Closed-Won and Closed-Lost reasons from Livespace custom fields migrate to Odoo's Lost Reason and Stage fields.

Livespace Spaces define separate working environments and process models. Odoo CRM uses a single pipeline with configurable Stages. We flatten multiple Spaces into one Odoo pipeline, mapping each Space's process steps to Odoo stage names in the sequence order. Probability percentages are computed from the average position of Deals within each Space's process.

Livespace Tasks linked to Deals migrate as Odoo CRM Tasks attached to the corresponding Opportunity via the res_model and res_id context fields. Task status (open/completed), due date, body text, and assignee resolve from the Livespace hubspot_owner_id to the Odoo res.users record by email match. Tasks linked to Persons migrate as Tasks on the Contact record.

Livespace Users are matched to Odoo res.users by email address. Any Livespace Owner with no corresponding Odoo User is flagged in a reconciliation queue for the customer's admin to provision before the migration proceeds. Team membership is preserved as Odoo Sales Team membership on the User record.

Livespace Teams map to Odoo CRM Sales Teams (crm.team model). Team-to-User memberships migrate as team membership records in Odoo. If the destination Odoo setup uses a single sales team, team assignments are flattened to individual User records.

Livespace Contact Groups (static segment lists) migrate to Odoo CRM Tags on the Contact record via the mail.activity.mixin model. Group membership is written as individual tag assignments per Contact. Dynamic groups that rely on filter rules cannot be reconstructed automatically and are documented as Odoo Segment criteria for the admin to configure.

Livespace Lead Sources (web form, referral, event, etc.) are exposed via the source list API. We map source values as a custom Char or Selection field on the Odoo Contact record. If the destination Odoo instance uses the CRM referral tracking module, source values can alternatively map to the campaign_id field for attribution reporting.

Livespace custom additional and hidden fields vary per account and are discovered via the Get custom fields endpoint before any transformation runs. We create matching custom fields on the Odoo res.partner model (for Person and Company fields) and crm.lead model (for Deal fields) via Odoo Studio. Picklist values are created as Selection options; date fields are normalised to the Odoo datetime format with UTC timezone handling.

Livespace does not expose file attachments via its public REST API. Attachments on Deals and Persons must be downloaded manually via the Livespace application UI or exported through its manual data export tool before migration begins. We flag this as a required pre-migration manual step in the runbook and exclude attachment records from the API-driven migration scope. Odoo's filestore remains empty for attachment content from Livespace.

Livespace's email sequence builder exposes no public API endpoints. Sequence membership, step status, and timing rules cannot be read programmatically. We document the full sequence configuration (step order, delay, template, trigger condition) in a written summary delivered alongside the migration so the customer's admin can manually rebuild using Odoo Mass Mailing, CRM Mail Automation, or a third-party sales engagement tool post-migration.