CRM migration

Migrate from Homesnap Pro to Odoo CRM

Field-level mapping, validation, and rollback between Homesnap Pro and Odoo CRM. We move data and schema; workflows are rebuilt natively in Odoo CRM.

Homesnap Pro logo

Homesnap Pro

Source

Odoo CRM

Destination

Odoo CRM logo

Compatibility

100%

12 of 12

objects map 1:1 between Homesnap Pro and Odoo CRM.

Complexity

BStandard

Timeline

2–5 business days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Homesnap Pro organized data around individual agents and their client interactions — contacts, showing requests, property matches, and market alerts tied to an MLS feed. The platform's data model is relatively flat: agent-managed contact records, property associations stored as custom properties on those contacts, and activity logs for showings and communications. CoStar discontinued Homesnap Pro as of October 23, 2023, replacing it with Homes Pro, making migration a data-retention problem rather than a discretionary upgrade. Odoo CRM stores contacts as res.partner records, prospects as crm.lead (which can be leads or opportunities depending on the stage), and manages sales teams via crm.team. The platform has no native real estate listing object, so MLS property data and agent-managed listings migrate as custom fields on crm.lead or as product records in Odoo's inventory module depending on how your team used Homesnap Pro. Activities (showings, calls, notes) map to mail.message and crm.activity records. We access Homesnap Pro data via its REST API using scoped read permissions. Odoo receives data via XML-RPC, which we use for bulk record creation and updates. Agent user accounts resolve by email match against Odoo res.users. A delta-pickup window captures any records modified during the cutover window. Agent performance metrics, lead scores, and pipeline stage assignments from Homesnap Pro require custom fields in Odoo since there is no equivalent native field.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Homesnap Pro logo

Homesnap Pro

What's pushing teams away

  • The platform was officially discontinued on October 23, 2023, with CoStar forcing all agents to migrate to Homes Pro or find an alternative.
  • The paid Concierge lead generation service delivered no qualified leads for multiple agents over 6-month periods, creating refund disputes and frustration.
  • Limited third-party integrations beyond the MLS feed required duplicate data entry across tools for marketing and transaction management.
  • G2 reviews cite an overall 3.0/5 rating with complaints about the gap between the free platform promise and the upsell-heavy Concierge program.
  • Agents reported that platform direction and support became unpredictable following the CoStar acquisition and subsequent product shutdown.

Choosing

Odoo CRM logo

Odoo CRM

What's pulling them in

  • Teams choose Odoo CRM for its modular architecture — one base install with one-click app additions means they can adopt CRM alone and add accounting, inventory, or sales later as the business grows.
  • Small businesses pick Odoo because the Community edition is free and open-source, with no per-user or contact limits, allowing full evaluation before committing to a paid Enterprise tier.
  • The drag-and-drop Kanban pipeline and AI lead scoring are highlighted across G2 reviews as concrete features that make lead management faster and more visual than spreadsheet-based workflows.
  • Odoo's native integration with email, live chat, SMS, VoIP, and WhatsApp means inbound leads from multiple channels feed into a single pipeline without third-party middleware.
  • Companies in retail, supply chain, and construction value that Odoo's CRM module shares the same PostgreSQL database and UI as its ERP modules, eliminating data silos between sales and operations.

Object mapping

How Homesnap Pro objects map to Odoo CRM

Each row shows how a Homesnap Pro object lands in Odoo CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Homesnap Pro

Contact (Client Record)

maps to

Odoo CRM

res.partner

1:1
Fully supported

Homesnap Pro client records map directly to Odoo res.partner. The contact's name, email, phone, and address fields translate 1:1. Owner (agent) assignment resolves by email match to Odoo res.users. Contacts with no email receive a generated placeholder address flagged for review.

Homesnap Pro

Contact (Prospect/Lead)

maps to

Odoo CRM

crm.lead

1:1
Fully supported

Homesnap Pro contacts that your agents tracked as prospects (not yet clients) map to Odoo crm.lead records. The crm.lead record type defaults to 'lead' status. Your team may convert these to 'opportunity' once a deal stage is reached, based on your Odoo pipeline configuration after migration. All prospect metadata, including lead source and agent assignment, transfers with the record.

Homesnap Pro

Agent Account

maps to

Odoo CRM

res.users

1:1
Fully supported

Homesnap Pro agent accounts map to Odoo res.users by email match. The agent's name, email, and phone transfer as user fields. Odoo requires each user to have a login — agents without an email on file get an admin-created account. Team assignment maps via crm.team.

Homesnap Pro

Property Listing (MLS)

maps to

Odoo CRM

crm.lead custom fields or product.product

1:1
Fully supported

Odoo has no native real estate listing object. MLS listing data (address, MLS ID, status, price) migrates as custom Char/Selection fields on crm.lead. Listings your team managed directly may alternatively map to product.product records in Odoo's inventory module — we determine this during discovery based on your data usage.

Homesnap Pro

Property Association (Contact ↔ Property)

maps to

Odoo CRM

crm.lead (linked property fields) + custom relation

1:1
Fully supported

Homesnap Pro stored which properties a contact was interested in or owned as associations on the contact record. These migrate as custom fields on crm.lead (e.g., Interested_Property_MLS_ID__c, Owner_Property_Address__c). For N:N relationships (contact interested in multiple properties), we create a custom link table in Odoo.

Homesnap Pro

Showing Request

maps to

Odoo CRM

crm.activity + custom fields on crm.lead

1:1
Fully supported

Showing requests in Homesnap Pro include property ID, client reference, requested date, assigned agent, and current status. We migrate these as Odoo crm.activity records with activity_type set to 'Showing' and add custom fields for the property reference and showing status. The original timestamp, agent owner, and requested scheduling information all transfer and remain preserved in Odoo.

Homesnap Pro

Market Alert

maps to

Odoo CRM

crm.activity (note subtype) + custom fields

1:1
Fully supported

Market alerts your agents sent to clients via Homesnap Pro become Odoo crm.activity notes with a 'Market Alert' subtype. The alert content, target contact, and send date map directly. Alert type (price drop, new listing, etc.) migrates as a custom selection field.

Homesnap Pro

Likelihood-to-List Score

maps to

Odoo CRM

Custom field on crm.lead

1:1
Fully supported

Homesnap Pro's predictive Likelihood-to-List feature generated a 0–100 score per homeowner. Odoo has no native equivalent. We preserve the score as a custom Integer field (Likelihood_to_List_Score__c) on crm.lead. The algorithm itself cannot be transferred — your team defines the new scoring logic in Odoo's lead scoring.

Homesnap Pro

Activity Log (Calls, Emails, Notes)

maps to

Odoo CRM

mail.message + crm.activity

1:1
Fully supported

Agent activity logs (calls logged, notes added, emails sent) in Homesnap Pro migrate to Odoo mail.message records linked to the relevant res.partner or crm.lead. Original timestamps, agent owner, and activity type preserved. Call duration and outcome stored as custom fields where present.

Homesnap Pro

Agent Performance Metrics

maps to

Odoo CRM

Custom report fields on crm.lead + Odoo Reporting

1:1
Fully supported

Homesnap Pro Business Suite tracked agent production metrics, rankings, and custom report data. This data lives in Odoo as custom fields on crm.lead (e.g., Agent_Previous_Close_Rate__c) and in Odoo's built-in reporting module. Historical metric snapshots migrate as read-only custom fields — actual pipeline tracking starts fresh in Odoo.

Homesnap Pro

Company/Brokerage Record

maps to

Odoo CRM

res.company + res.partner (commercial)

1:1
Fully supported

If your Homesnap Pro account stored brokerage or team-level organizational data, this migrates to Odoo res.company records. Agent-level contact information remains in res.partner. Odoo's multi-company model supports separate cost centers, franchise structures, or branch offices if your brokerage operates across multiple locations or divisions.

Homesnap Pro

Office/Team Hierarchy

maps to

Odoo CRM

crm.team

1:1
Fully supported

Homesnap Pro organized agents by office/team implicitly through MLS association. Odoo uses explicit crm.team records for this. We create Odoo crm.team records matching your Homesnap Pro team structure and assign agents (res.users) as team members via crm.team.member. Teams with multiple offices become separate crm.team records.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Homesnap Pro logo

Homesnap Pro gotchas

High

Platform shutdown creates a migration urgency gap

High

Closed API prevents programmatic data extraction

Medium

MLS listing data does not transfer between platforms

Medium

Concierge lead records are unreliable or missing

Odoo CRM logo

Odoo CRM gotchas

High

Odoo.sh version gating blocks assisted migrations from trial

High

Enterprise modules fail to install on Community after database restore

Medium

Custom module view inheritance breaks between Odoo major versions

Medium

Custom fields risk losing their application context on Community

Low

API access for Community is gated behind the Custom Plan

Pair-specific challenges

  • Homesnap Pro shutdown creates a hard migration deadline

    CoStar discontinued Homesnap Pro on October 23, 2023, replacing it with Homes Pro. Any data remaining in Homesnap Pro after the shutdown window has limited export support. We recommend initiating migration planning immediately to ensure your export is complete before API access is fully deprecated. If you have already missed the window, we can work with whatever partial export your account still provides, but some historical showing and activity data may be unrecoverable at that point.

  • Homesnap Pro has no native lead/opportunity split — Odoo requires one

    Homesnap Pro tracked prospects and clients in a single contact record with a client_type flag. Odoo separates crm.lead (prospect) from opportunity (a stage within crm.lead after conversion). We map all Homesnap Pro non-client contacts to Odoo crm.lead in the 'new' stage, but your team needs to define which stage represents a converted opportunity in your Odoo pipeline. Without explicit stage mapping, leads appear active but will not trigger pipeline metrics until manually moved through the stage sequence.

  • MLS listing data requires Odoo custom fields — no native equivalent

    Homesnap Pro's core data product is MLS listing information tied to contacts and showing requests. Odoo CRM has no real estate listing object. Every listing-related field (MLS number, listing status, property details, showing associations) must be defined as a custom field on crm.lead or stored in a separate product record. This means your Odoo setup requires custom field development before data lands — we handle the field creation, but you need to decide which custom fields map to which Odoo objects during the planning phase.

  • Agent performance metrics and pre-built reports do not transfer

    Homesnap Pro Business Suite includes agent production reports, rankings, and custom report generation. These exist as calculated outputs, not raw data. Odoo has a reporting module that can reconstruct similar metrics, but the pre-built reports themselves must be rebuilt. We preserve the underlying data (closed deals, listing count, showing activity) as custom fields on crm.lead so your Odoo admin can build equivalent reports, but the report templates themselves require manual recreation in Odoo's report designer.

  • Odoo XML-RPC rate limits affect bulk import speed on large datasets

    Odoo's XML-RPC API has per-request overhead that becomes significant when loading tens of thousands of records. Homesnap Pro migrations with over 50,000 contact records or heavy activity logs may require batch processing with retry logic to handle Odoo's internal locking. We throttle imports and run during off-peak hours to minimize contention, but large migrations take longer than equivalent Salesforce or HubSpot migrations due to Odoo's synchronous request model. We quote timelines based on dataset size after discovery.

Migration approach

Six steps for a successful Homesnap Pro to Odoo CRM data migration

  1. Discover your Homesnap Pro data inventory

    We connect to your Homesnap Pro account via scoped read-only API access and extract a full inventory of records: contacts, agents, property associations, showing requests, market alerts, and activity logs. We generate a data quality report identifying duplicate contacts, missing email addresses, and records with incomplete property associations. This report drives the migration plan and identifies which records need custom field handling in Odoo versus standard field mapping.

  2. Design Odoo schema for real estate CRM

    Based on the discovery output, we define the Odoo custom fields needed to capture Homesnap Pro data that has no native equivalent. This includes property-related fields on crm.lead (MLS number, listing status, bedrooms, square feet), likelihood-to-list score fields, showing status fields, and any agent performance snapshot fields. We create a schema setup guide for your Odoo admin to apply these fields before the data load. If you use Odoo Community, we provide the fields.xml data file for import; Enterprise users can create fields via Settings > Technical.

  3. Resolve agents and map teams

    Homesnap Pro agent accounts resolve against Odoo res.users by email match. Agents without an Odoo login receive an admin-created account request before migration. Team structure from Homesnap Pro (office/MLS association) maps to Odoo crm.team records. We flag any agent who has left your brokerage so their records can be assigned to a fallback owner before migration — no record lands without an Odoo owner.

  4. Run sample migration with field-level diff

    We run a test migration against a sample of 100–500 records — spanning contacts, leads, listings, and activities — and generate a field-level diff report. This report shows every mapped field, its source value in Homesnap Pro, and its destination value in Odoo. You verify that listing data landed in the right custom fields, that stage mappings reflect your pipeline logic, and that agent ownership resolved correctly. We fix any mapping errors before the full run commits.

  5. Execute full migration with delta pickup

    The full data load runs against your Odoo instance using XML-RPC for record creation and update. A delta-pickup window (typically 24–48 hours) runs in parallel, capturing any records created or modified in Homesnap Pro during the migration window. After the main load completes, we run the delta pass and reconcile counts. An audit log documents every operation. If reconciliation reveals missing records or mismatched counts, one-click rollback reverts the Odoo instance to its pre-migration state for a clean retry.

  6. Post-migration validation and export workflow definitions

    We deliver a validation report comparing Homesnap Pro record counts against Odoo record counts per object, flagging any discrepancies for manual review. We also export your Homesnap Pro workflow definitions (showing request logic, alert rules) as a written reference document your Odoo admin can use to rebuild equivalent automations using Odoo's crm.activity and mail.thread models. Workflows do not migrate automatically — this document serves as the rebuild brief.

Platform deep dives

Context on both ends of the pair

Homesnap Pro logo

Homesnap Pro

Source

Strengths

  • Real-time MLS data integration directly in the mobile app with no manual data entry.
  • Free tier bundled with MLS membership eliminated per-agent software costs for most brokerages.
  • Likelihood to List predictive algorithm surfaced pre-market seller leads before competitors.
  • Business Suite gave brokers a recruiting and team performance reporting tool at the organization level.
  • Mobile-first UX was consistently praised for ease of use in G2 and Capterra reviews.

Weaknesses

  • Platform shut down October 23, 2023 — all agents forced to migrate or switch platforms.
  • Closed API with no documented export endpoints made programmatic data extraction impossible.
  • No reliable public bulk export path — agents depend on what transferred at CoStar-forced shutdown.
  • Concierge lead generation service widely reported to deliver zero qualified leads, undermining the paid tier value.
  • Photos and MLS imagery are not exportable due to CDN restrictions and MLS licensing terms.
Odoo CRM logo

Odoo CRM

Destination

Strengths

  • Modular open-source architecture lets teams start with CRM and add ERP apps as needs grow, all sharing one PostgreSQL database.
  • Free Community edition with no contact limits and full source code access means zero licensing cost for evaluation and small deployments.
  • Drag-and-drop Kanban pipeline with AI lead scoring gives a visual, prioritized view of the sales funnel without requiring custom configuration.
  • Native integrations with email, live chat, SMS, VoIP, WhatsApp, and social media feed all inbound leads into a single unified inbox.
  • Active Odoo Community Association (OCA) maintains dozens of community-maintained modules on GitHub for extended functionality.

Weaknesses

  • Gmail and email integration reliability is a recurring complaint — threads drop and conversations scatter across inboxes, disrupting sales team workflows.
  • Enterprise edition pricing stacks quickly: multiple apps at per-user rates ($25–$50/user/month) plus Odoo.sh hosting costs more than many SMBs anticipate.
  • Setup and configuration complexity increases significantly once custom fields, automation rules, and multiple installed modules are in play.
  • Odoo.sh trial databases run on a version (e.g., 18.3) that is not directly migratable to Odoo.sh, blocking the assisted migration path Odoo advertises.
  • Version upgrades between major Odoo releases (e.g., 17→18) frequently break custom module view definitions and XPath expressions, requiring manual remediation.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Homesnap Pro and Odoo CRM.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Homesnap Pro: Not publicly documented.

  • Data volume sensitivity

    B

    Homesnap Pro doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Homesnap Pro to Odoo CRM migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Homesnap Pro to Odoo CRM data migrations

Answers to the questions buyers ask most during Homesnap Pro to Odoo CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Homesnap Pro to Odoo CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Homesnap Pro to Odoo CRM migrations complete in 2–5 business days for under 25,000 records. Larger teams with 100,000+ records, complex MLS listing data, or multi-office Odoo configurations extend to 2–4 weeks. The longest phase is usually custom field setup and sample validation — the actual data load via XML-RPC runs overnight for most mid-size datasets. We provide a timeline estimate after reviewing your Homesnap Pro data export.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Homesnap Pro.
Land in Odoo CRM, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day