Migrate from Anyone Home to Odoo CRM

Anyone Home Prospect maps directly to Odoo crm.lead. Prospect fields (name, email, phone, source) map to crm.lead fields directly. Prospect stage in Anyone Home (Inquiry, Touring, Application, Lease Signing) maps to crm.stage values within the designated Odoo pipeline. Original create dates are preserved in a custom datetime field since Odoo's crm.lead create_date reflects migration time.

Prospects that have moved past the inquiry stage in Anyone Home (Touring or Application) migrate as Odoo crm.lead with type='opportunity'. Odoo's Convert to Opportunity action is not triggered automatically — instead, we set the crm.lead type flag directly so the record lands in Odoo's Opportunity pipeline view immediately. This preserves the lease-stage history without manual conversion steps.

Anyone Home Contact maps to Odoo res.partner. Odoo res.partner serves as both contact and company record — for individual contacts, company_id is set to the associated property company or left empty with type='contact'. Email, phone, address fields map directly using Odoo's standard field names. Partner type (customer, vendor) is assigned based on Anyone Home contact role.

Anyone Home property records (units, floor plans, rent amounts) do not have a direct Odoo CRM equivalent. If Odoo Inventory or Sales is installed, these migrate as product.product or stock_quant records. The property-unit association on a prospect is stored as a custom many2one field on crm.lead pointing to the product.product record. This requires Odoo's Inventory or Sales app to be active — we confirm this before migration.

Active lease applications in Anyone Home (Lease Signing stage) map to Odoo sale.order records when Odoo Sales is present. Deal amount (rent value, lease term) maps to order lines on sale.order. If Odoo Sales is not active, the lease deal migrates as a crm.lead with custom fields capturing rent amount, lease start date, and lease term — the deal is not lost but is not a full sale.order until Sales is enabled.

Anyone Home stores lead source (Organic, Paid, Referral, ILS, Walk-in) per prospect. Odoo's utm.source model is available when Odoo Marketing is installed. For CRM-only migrations, we store the source value as a custom selection field x_lead_source on crm.lead. When Odoo Marketing is active, we link the source to the utm.source record for full attribution reporting.

Anyone Home communication logs (automated messages, call logs, meeting notes tied to prospects) migrate as Odoo mail.message records linked to the crm.lead. Original timestamps and owner IDs are preserved. Odoo's mail_thread model on crm.lead handles activity history display in the CRM view. Automated message templates from Anyone Home are not migrated — they are exported as JSON for manual Odoo email template recreation.

Anyone Home user assignments on prospects and deals are resolved by email match against Odoo res.users records. If a Anyone Home user email has no matching Odoo user, the record is assigned to the migration fallback user (configurable) and flagged for admin review. Owner resolution happens before the main migration run to prevent orphaned records.

Anyone Home documents attached to prospects (application PDFs, ID scans, lease agreements) are downloaded and re-uploaded as Odoo ir.attachment records linked to the crm.lead or res.partner. Odoo's filestore handles storage. File size limits (default 25MB per file in Odoo Online) are respected; oversized files are split or linked by URL.

Anyone Home custom properties at the prospect level (e.g., referral_agent_name, preferred_move_in_date, unit_preference) require Odoo custom field creation via Python module inheritance on crm.lead. We create the custom fields before migration, then map values during the migration run. If Odoo Studio is available, custom fields can be created via the UI without code — we use whichever method is accessible in the destination environment.

Anyone Home leasing workflows (automated follow-up emails, renewal alerts, stage-change triggers) have no Odoo equivalent at the migration-data level. We export the workflow definitions as a structured JSON file listing trigger conditions, action types, and timing rules so the Odoo admin can recreate them using Odoo's Automated Actions (Settings > Technical > Automated Actions) or Studio-based workflow builder.

Anyone Home portfolio or regional groupings of properties map to Odoo crm.team. Each portfolio becomes a crm.team in Odoo, with team members assigned via Odoo's team membership model. This scopes Odoo pipeline views to team-specific stages and gives managers a team-level dashboard without cross-team data visibility leakage.