Migrate from BoldTrail BackOffice to Odoo CRM

Transaction properties stored as unstructured JSON collapse into flat custom fields

BoldTrail transaction metadata (compliance form IDs, HOA fees, inspection dates, split percentages) is stored as named properties on the transaction object, each a discrete API-accessible field. Odoo's crm.lead model has no native equivalent — we must create individual custom fields (char, date, monetary, float) for each named property during the schema-setup phase. If BoldTrail stores these values inside a generic 'properties' JSON blob rather than as named fields, the JSON must be parsed and flattened before mapping, which requires a data-profiling step before migration runs. Custom fields that do not exist in Odoo at load time will silently drop — we catch this by validating the field registry against the property list before the migration begins.

BoldTrail e-signature token URLs are not transferable and documents must be re-signed

BoldTrail e-signature links point to BoldSign token URLs scoped to the BoldTrail account — those tokens are invalidated when the account is deactivated or when the document is accessed outside BoldTrail. Odoo has no native BoldSign integration; Odoo Sign is the native equivalent but requires a separate subscription and new signature requests. We preserve the original signed PDF as an Odoo ir_attachment and record the signatory email and original timestamp in custom fields on the lead. However, the document's legal standing in Odoo depends on a fresh signature cycle. We flag every transaction with an e-signature for manual re-signing coordination with all parties post-migration before closing the BoldTrail account.

Agent-to-user split requires manual provisioning for inactive or admin-only agents

BoldTrail agents who are active sellers need Odoo res.users accounts so they can own leads and log activities — these require an email login and a named user license in Odoo Enterprise. Agents who are brokers, office admins, or inactive agents do not need Odoo login. We identify which BoldTrail agents need Odoo user accounts during discovery by checking their role and activity flag. Any agent with a duplicate email across multiple BoldTrail brokerages in the same Odoo instance will conflict on the Odoo login uniqueness constraint and must be resolved before migration. Agents without a valid email in BoldTrail cannot auto-provision as Odoo users and fall back to res.partner-only records.

Commission split percentage logic requires Odoo Sales app for automated calculation

BoldTrail stores commission split percentages per agent as flat fields on the transaction record (e.g., AgentASplit: 60, AgentBSplit: 40). These values migrate correctly as custom float fields on the crm.lead. However, BoldTrail's automated next-day ACH disbursement logic — triggered when a transaction status changes to Closed — has no Odoo equivalent in the base CRM module. Odoo's Sales app with payment terms can replicate tiered commission rules, but this is a separate configuration step. We preserve the split percentages as lead fields and deliver a commission-rule specification document so your Odoo admin can configure automated disbursements in the Sales app's payment-term rules after go-live.

BoldTrail file downloads require bulk API iteration — UI exports are per-transaction

BoldTrail's web UI exports files one transaction at a time. For bulk migration of document attachments, we use the BoldTrail file API to iterate all transactions and download attachments concurrently. The BoldSign API rate limit of 2,000 requests per hour per account applies to file downloads if BoldSign is used as the underlying e-signature provider. For brokerages with 1,000+ transactions each containing 5–10 attachments, this can take 3–6 hours within rate-limit throttling. We run download jobs in off-peak hours to avoid hitting limits during business use. Attachments exceeding Odoo's default 25MB per-file size are flagged for chunked upload or alternative cloud-storage linking.