Migrate from Lofty to Odoo CRM

Lofty leads map directly to Odoo crm.lead records. The crm.lead type field distinguishes between 'lead' and 'opportunity' states. Lofty lead status (New, Contacted, Qualified, etc.) maps to Odoo stage_id values. Original create dates preserved in crm.lead.create_date or a custom field.

Lofty transactions are deal records that map to Odoo crm.lead in 'Opportunity' state. Lofty's deal amount, close date, and stage map to planned_revenue, date_deadline, and stage_id respectively. The crm.lead partner_id links to the primary contact from the original transaction, maintaining the relationship between deals and their associated contacts.

Lofty agents map to Odoo res.users by email address match. Agent names become user names, and agent email becomes the Odoo login credential. User groups_id determines CRM access level (Sales, Manager, Administrator). Unmatched agents are flagged for team invitation or fallback assignment to a default user.

Lofty teams map to Odoo crm.team records. Each Odoo team has its own pipeline stages defined in crm.stage with team_id scoped to that specific team. Lofty agents assigned to a team receive crm.team membership in Odoo via res.users belongs_to teams relationship.

Lofty company records (if any) map to Odoo res.partner with is_company=True set. Parent-child relationships between companies in Lofty translate to parent_id on the res.partner records. Contact records link to their parent company through that same parent_id field when a company exists in the source data.

Lofty property records map to Odoo product.product for real estate listings. Property name becomes product name, listing type becomes product category (categ_id), price maps to list_price, and property details become description fields. Bedrooms, bathrooms, and square footage become custom fields on the product record.

Lofty tags on leads and transactions map to Odoo crm.tag records. Tags on crm.lead use the tag_ids many2many field for assignment. Multi-tag assignments on a single Lofty record create multiple tag_ids entries on the corresponding Odoo crm.lead, preserving all categorization from the source.

Lofty note entries map to Odoo mail.message records on the related crm.lead. Original timestamps and author (agent) information is preserved through the migration. Activity logs including calls and meetings map to mail.activity with activity_type_id distinguishing between different interaction types.

Lofty lead source values (Website, Referral, Zillow, Realtor.com, etc.) map to Odoo utm.source records via crm.lead source_id field. Each unique Lofty source string creates a corresponding utm.source record in Odoo for accurate attribution reporting. Leads without a source receive a default utm.source assignment.

Lofty custom fields require Odoo custom field creation before migration begins. Text fields map to char or text depending on length constraints. Number fields map to float or integer types based on precision needs. Single-select maps to selection or many2one referencing a dedicated model. Multi-select maps to char (comma-separated) or many2many — your admin chooses the preferred storage approach.

Lofty file attachments on leads and transactions migrate to Odoo ir.attachment records linked to the crm.lead via res_model and res_id reference fields. Files are re-uploaded to Odoo's filestore during migration. File size limits apply per Odoo configuration settings with a default maximum of 25MB per file upload.