How long does an Agentbox to Odoo CRM migration take?

Most Agentbox-to-Odoo CRM migrations complete in 48–72 hours for under 50,000 records. Configurations with extensive appraisal history, large listing databases, or multi-branch agency setups extend to 5–7 days. The longest single step is usually the custom field design and Odoo schema setup before migration begins, not the data transfer itself. For agencies with over 500,000 records or complex appraisal-history structures, timeline extends to 5–7 days, with the delta-pickup window adding additional time after the initial migration run.

Will my Agentbox workflows and automations migrate to Odoo CRM?

No. FlitStack AI migrates data and schema only — workflow rules, automations, and sequences in Agentbox do not transfer to Odoo. They must be rebuilt using Odoo Automations, Server Actions, or the Odoo Studio workflow builder. We export your Agentbox workflow definitions as a structured reference document that your Odoo admin can use to rebuild each automation in Odoo. This includes trigger conditions, action sequences, and any conditional logic that was configured in Agentbox for your agency's sales processes.

What does an Agentbox listing become in Odoo CRM?

Agentbox listings have no direct Odoo equivalent. Listing data (address, suburb, price, bedrooms, bathrooms, property_type) migrates as custom fields on the vendor's res.partner record. Active listings also generate a crm.lead record with type=Opportunity so they appear in the pipeline kanban view. The REA Group listing ID is preserved as a custom Char field for post-migration re-integration with the REA API.

Can I migrate Agentbox custom fields to Odoo custom fields?

Yes. Agentbox custom fields on contacts, listings, and appraisals map to Odoo custom fields on the target object. We create the Odoo custom fields (Char, Selection, Float, Date, Integer) before migration and map source values field-by-field. Pick-list values in Agentbox are translated to Odoo Selection field options via a value-mapping table. Custom fields are documented in the pre-migration schema plan.

What happens to Agentbox appraisal history in Odoo CRM?

Agentbox appraisal records migrate as crm.lead records with type='Appraisal' and a dedicated pipeline stage named 'Appraisal Complete'. Original estimated values and appraisal dates are preserved in custom fields (estimated_value__c, appraisal_date__c) on the crm.lead record. The vendor contact and property address link to the res.partner record, maintaining the relationship context. Odoo's activity timeline attaches to the crm.lead so the full appraisal history with notes and agent assignments is visible in one consolidated view.

Does the migration affect my Agentbox account during cutover?

No. FlitStack AI uses read-only API access to Agentbox during the migration — your team keeps working in Agentbox throughout the process. A delta-pickup window of 24–48 hours after the initial migration run captures any new or modified records created during the cutover. No changes are made to Agentbox data; the account remains fully functional until you decide to decommission it.

How are Agentbox agent records handled in the migration?

Agentbox agent records are split into two Odoo objects: a res.users record (for login and task assignment) matched by email, and a res.partner contact record for the agent's own client profile. Agents without a resolvable email are flagged in the pre-migration resolution report — your Odoo admin must create their Odoo user accounts before migration or assign their records to a fallback owner. Contact and listing owner_id fields in Odoo reference the resolved res.users record.

Agentbox to Odoo CRM Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Agentbox is a property-first CRM built on the Reapit platform for Australian real estate agencies. Its data model centers on contacts associated with properties, agencies with agent records, listings tied to vendors and buyers, and appraisal history per property. Odoo CRM uses a fundamentally different architecture: crm.lead stores leads and opportunities, res.partner stores both companies and individual contacts, and property data must be carried as custom fields or related records. The migration therefore requires restructuring how property associations are represented — contacts migrate into res.partner, agencies into parent company records, and property details (address, price, type, bedrooms) into custom fields on the partner record. Agent records resolve to Odoo users by email match, and appraisal history migrates as custom activity records with original timestamps. We use the Reapit Agentbox API for export and Odoo's XML-RPC interface for import, handling value mapping on pick-lists, owner resolution, and relationship reconstruction throughout. Automation logic, workflow rules, and REA Group listing integrations do not migrate — those require Odoo-side rebuild using Odoo Automations and the official Odoo apps marketplace.

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

Agentbox

What's pushing teams away

Past appraisal records cannot be migrated and must be recreated manually after go-live, creating a gap in historical data for agencies with long sales histories.
Prospecting map views and CoreLogic live data are Agentbox-native integrations that do not transfer to competing platforms, forcing agents to rebuild their market intelligence workflow.
Agencies using unsupported CRM source systems must engage a third-party specialist at additional cost, with Agentbox charging $800 plus GST on top of the specialist's reformatting fees.
Website customisation settings including property tile layouts and filter configurations do not export via the standard migration path and require manual reconfiguration.

Choosing

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 Agentbox objects map to Odoo CRM

Each row shows how a Agentbox 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.

Agentbox

Contact

maps to

Odoo CRM

res.partner

1:1

Fully supported

Agentbox contacts map to Odoo res.partner records. The partner record holds name, email, phone, and address fields natively. Primary property association migrates as a custom Char field (primary_property_id) on the partner record for reference and future property linkage in Odoo.

Agentbox

Agency / Company

maps to

Odoo CRM

res.partner (company)

1:1

Fully supported

Agentbox agency records map to res.partner records with is_company=True. The company name populates the name field, and trading_name or ABN migrates into custom fields for regulatory compliance. Child agent contacts link to the agency via parent_id on the partner record, maintaining the organizational hierarchy.

Agentbox

Agent

maps to

Odoo CRM

res.users + res.partner

1:1

Fully supported

Agentbox agent records split into two Odoo objects: the agent profile becomes a res.users record (matched by email) for login and task assignment, and the agent-as-contact becomes a res.partner record for their own client profile. Unmatched agents are flagged before migration so Odoo user accounts can be provisioned first.

Agentbox

Listing

maps to

Odoo CRM

crm.lead (custom) + res.partner fields

1:1

Fully supported

Agentbox listings have no native Odoo equivalent. Listing data (address, suburb, price, property_type, bedrooms, bathrooms, car_spaces, listing_status) migrates as custom fields on res.partner. Active listings also create a crm.lead record with type='Opportunity' so the pipeline view can display them alongside other opportunities.

Agentbox

Listing Vendor / Landlord

maps to

Odoo CRM

res.partner (parent)

1:1

Fully supported

The vendor or landlord on an Agentbox listing is a contact record. That contact already maps to res.partner per the Contact mapping above. The listing's vendor association links via the custom property_id field on the partner record, maintaining the relationship between vendor and their listed properties.

Agentbox

Listing Buyer / Tenant prospect

maps to

Odoo CRM

res.partner + crm.lead

1:1

Fully supported

Buyers and tenant prospects on a listing map to res.partner directly, and where a deal pipeline stage exists, a crm.lead is created with the opportunity_name referencing the listing address. Buyer requirements (price range, features) migrate as custom fields on the partner record for future reference and matching.

Agentbox

Appraisal

maps to

Odoo CRM

crm.lead (type=Appraisal)

1:1

Fully supported

Agentbox appraisal records (estimated_value, appraisal_date, appraisal_type, notes) have no Odoo native equivalent. They migrate as crm.lead records with type set to 'Appraisal', stage set to a dedicated 'Appraisal Complete' stage, and custom fields estimated_value__c and appraisal_date__c carrying original values and timestamps.

Agentbox

Task / Activity

maps to

Odoo CRM

mail.activity

1:1

Fully supported

Agentbox tasks map to Odoo mail.activity records. The activity_type, user_id (owner), date_deadline, and summary carry over accurately. Original create dates are preserved in a custom datetime field since Odoo's create_date reflects the migration run, maintaining historical activity timelines.

Agentbox

Contact Category / Tag

maps to

Odoo CRM

res.partner.category

1:1

Fully supported

Agentbox contact categories (tags) map to Odoo res.partner.category records. Tags are created in Odoo first using the same names, then linked to partner records via the res_partner_category_rel many-to-many table during migration, preserving all categorization groupings.

Agentbox

Open Home Attendees

maps to

Odoo CRM

res.partner + mail.activity

many:1

Fully supported

Agentbox records open home attendee contacts and their enquiry details. These merge into res.partner for the attendee and a mail.activity record capturing the home-open event date and property address. If the attendee is already in the system by email, the existing partner record is linked to avoid duplicates.

Agentbox

REA Listing ID

maps to

Odoo CRM

Custom Char field on res.partner

1:1

Fully supported

Agentbox imports listing history from the REA Group API and stores a rea_listing_id on each listing. This ID migrates as a custom Char field (rea_listing_id__c) on the partner record so that Odoo integrations can re-connect to the REA API after migration is complete.

Agentbox

Enquiry / Lead Source

maps to

Odoo CRM

crm.lead (source_id)

1:1

Fully supported

Agentbox enquiry sources (buyer enquiry, vendor appraisal, website, REA) map to Odoo crm.lead source_id values via a lookup table. Source names are created as utm.source records in Odoo and linked during migration for accurate lead source reporting. Unknown sources are flagged for manual assignment by your Odoo admin.

Agentbox	Odoo CRM	Compatibility
Contact	res.partner1:1	Fully supported
Agency / Company	res.partner (company)1:1	Fully supported
Agent	res.users + res.partner1:1	Fully supported
Listing	crm.lead (custom) + res.partner fields1:1	Fully supported
Listing Vendor / Landlord	res.partner (parent)1:1	Fully supported
Listing Buyer / Tenant prospect	res.partner + crm.lead1:1	Fully supported
Appraisal	crm.lead (type=Appraisal)1:1	Fully supported
Task / Activity	mail.activity1:1	Fully supported
Contact Category / Tag	res.partner.category1:1	Fully supported
Open Home Attendees	res.partner + mail.activitymany:1	Fully supported
REA Listing ID	Custom Char field on res.partner1:1	Fully supported
Enquiry / Lead Source	crm.lead (source_id)1:1	Fully supported

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.

Agentbox gotchas

High

Appraisal records excluded from all migration tiers

High

Approved data source list gates basic migration

Medium

Third-party migration incurs layered fees

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

Agentbox gotchas		Odoo CRM gotchas
Severity	Issue	Severity	Issue
High	Appraisal records excluded from all migration tiers	High	Odoo.sh version gating blocks assisted migrations from trial
High	Approved data source list gates basic migration	High	Enterprise modules fail to install on Community after database restore
Medium	Third-party migration incurs layered fees	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

Property-first model requires structural translation into Odoo's contact-centric architecture

Agentbox organizes data around properties — every contact, listing, and appraisal links to a property_id. Odoo CRM has no native property entity; res.partner and crm.lead are the primary objects. We reconstruct property associations as custom Char fields on res.partner (listing_address__c, rea_listing_id__c) and create a crm.lead with type=Opportunity for each active listing. Agencies must decide whether to create one partner record per property or one per vendor — we surface both approaches in the pre-migration schema plan and let your Odoo admin choose before data lands.
Appraisal history has no native Odoo equivalent and requires custom model design

Agentbox appraisal records (estimated_value, appraisal_date, appraisal_type) are standalone objects tied to a property. In Odoo, these require a custom design: we create crm.lead records with type='Appraisal', a dedicated pipeline stage named 'Appraisal Complete', and custom fields estimated_value__c and appraisal_date__c to preserve original values. The crm.lead model is used because it natively supports user_id assignment, stage tracking, and the mail.activity timeline. However, appraisal-specific reporting requires Odoo-side configuration of a custom dashboard view grouping by the appraisal_type__c field.
Agent-to-Odoo-user email matching leaves unmatched agents that need pre-migration provisioning

Agentbox agent records do not automatically map to Odoo res.users because Agentbox agents and Odoo users use different identity systems. We match by email address — an agent with [email protected] creates a res.users record with that email. Agents without a matchable email are flagged in a pre-migration report. Your Odoo admin must either invite those agents to Odoo before migration or assign their records to a fallback user. If this step is skipped, contact and listing owner_id fields land as null, breaking activity assignment in Odoo's sales team view.
REA Group listing import does not transfer — rea_listing_id stored for post-migration re-integration

Agentbox's native integration with the REA Group API imports current and historical listing data directly from REA's platform. This API connection does not migrate to Odoo — there is no Odoo native REA connector in the standard Odoo apps. We preserve the rea_listing_id on each partner record as a custom Char field (rea_listing_id__c). After migration, your team can reconnect REA listings using Odoo's REST API integration capabilities, the Odoo Apps Store REA connector modules, or the OCA community module if available for your Odoo version. This is disclosed explicitly so no one expects the listing-sync to resume automatically.
Odoo API rate limits on standard plans require batched migration runs

Odoo's XML-RPC interface on standard Odoo Online and Odoo.sh plans enforces a rate limit of approximately 1 request per second for authenticated sessions. Large Agentbox databases (10,000+ listings, 50,000+ contacts) require batching with retry logic and staggered execution windows. We implement exponential back-off on 403 and 429 responses and resume from the last checkpoint if a batch fails. For agencies with over 100,000 records, we recommend scheduling migration during off-peak hours to maximize available API throughput and reduce total migration clock time.

Migration approach

Six steps for a successful Agentbox to Odoo CRM data migration

Export Agentbox data via Reapit OpenPlatform API

FlitStack AI connects to the Agentbox Reapit OpenPlatform API using your agency credentials. We export contacts, companies/agency records, agent profiles, listings, appraisal history, tasks, contact categories, and open-home attendee records in a single coordinated pull. Each record type is exported with its internal ID, create_date, write_date, and owner agent_id preserved. The export runs read-only — your team continues working in Agentbox throughout. We store a snapshot timestamp so the delta window is anchored precisely.
Audit schema and design Odoo custom field structure

We analyze your Agentbox field inventory — identifying custom fields, pick-list values, and relationship IDs — and produce an Odoo schema design document. This specifies which custom fields to create on res.partner (listing_*, preferred_suburb, buyer_status, rea_listing_id), which crm.lead fields to use for appraisals, and which tags to map to res.partner.category. Your Odoo admin creates the custom fields and pipeline stages in the target Odoo instance before we begin the test migration. This ensures data validates on first landing.
Resolve agent-to-user mapping by email

Agentbox agent records are matched to Odoo res.users by email address during the pre-migration audit phase. We generate a comprehensive pre-migration resolution report listing all matched agents, unmatched agents, and the suggested fallback owner for each unmatched agent's records and related contacts. Your Odoo admin provisions missing users or confirms fallback assignments before migration begins. No contact or listing record lands without a resolved owner_id, ensuring proper task and activity assignment from day one.
Run sample migration with field-level diff

A representative slice migrates first — typically 200–500 records spanning contacts, agencies, listings, and appraisal records. We generate a field-level diff comparing source values against Odoo destination values, verifying that custom field labels, pick-list values, and owner assignments are correct. You review the diff report and approve before the full run. This catches mapping errors before they scale across the entire database.
Execute full migration with delta-pickup window

The full migration runs in sequenced batches: agencies first (for parent_id resolution), then contacts, then listings and appraisals, then tasks and attendee records. After the initial run completes, a 24–48 hour delta-pickup window captures any records modified or created in Agentbox during the cutover period. Audit log records every operation. One-click rollback reverts the Odoo database to its pre-migration state if reconciliation identifies data integrity issues.

Platform deep dives

Context on both ends of the pair

Agentbox

Source

Strengths

Top-ranked Australian real estate CRM with documented market penetration among REB Top 100 agencies.
Native integration with REA Group property feeds and CoreLogic live market data within prospecting workflows.
Bundled website builder eliminates the need for a separate agency website vendor.
Consistent desktop, tablet, and mobile experience for agents working in the field.
Internal managed migration team for approved source CRMs reduces onboarding friction.

Weaknesses

Historical appraisal records cannot be migrated and must be re-created manually after cutover.
Approved source CRM list is narrow; everyone else routes through a paid third-party specialist plus a flat receiving fee.
No public API documentation, making custom integrations dependent on Agentbox engagement.
Website customisation and prospecting map layers do not export, creating switching cost for agencies moving away.
Pricing is opaque — no rate card published — making cost-benefit comparisons require a sales call.

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.

	Agentbox Source	Odoo CRM Destination
Strengths	Top-ranked Australian real estate CRM with documented market penetration among REB Top 100 agencies. Native integration with REA Group property feeds and CoreLogic live market data within prospecting workflows. Bundled website builder eliminates the need for a separate agency website vendor. Consistent desktop, tablet, and mobile experience for agents working in the field. Internal managed migration team for approved source CRMs reduces onboarding friction.	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	Historical appraisal records cannot be migrated and must be re-created manually after cutover. Approved source CRM list is narrow; everyone else routes through a paid third-party specialist plus a flat receiving fee. No public API documentation, making custom integrations dependent on Agentbox engagement. Website customisation and prospecting map layers do not export, creating switching cost for agencies moving away. Pricing is opaque — no rate card published — making cost-benefit comparisons require a sales call.	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.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Agentbox to Odoo CRM

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Agentbox

Odoo CRM

How Agentbox objects map to Odoo CRM

What specifically takes care here

Six steps for a successful Agentbox to Odoo CRM data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Agentbox to Odoo CRM migration cost

What are you migrating?

Frequently asked questions about Agentbox to Odoo CRM data migrations

Can't find your answer?

Related migrations to explore

Move from Agentbox.
Land in Odoo CRM, intact.

Migrate from Agentbox to Odoo CRM

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Agentbox

Odoo CRM

How Agentbox objects map to Odoo CRM

What specifically takes care here

Six steps for a successful Agentbox to Odoo CRM data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Agentbox to Odoo CRM migration cost

Frequently asked questions about Agentbox to Odoo CRM data migrations

Can't find your answer?

How long does an Agentbox to Odoo CRM migration take?

Will my Agentbox workflows and automations migrate to Odoo CRM?

What does an Agentbox listing become in Odoo CRM?

Can I migrate Agentbox custom fields to Odoo custom fields?

What happens to Agentbox appraisal history in Odoo CRM?

Does the migration affect my Agentbox account during cutover?

How are Agentbox agent records handled in the migration?

Related migrations to explore

Move from Agentbox. Land in Odoo CRM, intact.

Move from Agentbox.
Land in Odoo CRM, intact.