Migrate from Wealthengine to Odoo CRM

WealthEngine wealth attributes require Odoo custom fields — Studio has functional limits

WealthEngine profiles routinely carry 20–40 enrichment fields per record (P2G scores, asset valuations, giving indicators, planned giving flags, RFM ratings). Odoo CRM's standard res.partner model exposes a limited set of default fields. The remaining wealth data must be created as custom fields. Odoo Studio allows field creation in the UI for Enterprise plans, but fields created purely in Studio are not version-controlled and can be lost during module upgrades — FlitStack recommends delivering custom fields via a custom module (x_ prefixed fields defined in Python) so they survive Odoo version upgrades. Community edition users must use a custom module approach regardless, as Studio is Enterprise-only.

N:N contact-to-company associations collapse to a single parent_id on res.partner

WealthEngine allows one contact profile to link to multiple organizations — a board member's personal profile can associate with their employer company and a nonprofit board simultaneously. Odoo res.partner enforces a single parent_id for the company relationship. Contacts who have multiple organizational affiliations in WealthEngine must be resolved to one primary company in Odoo; additional affiliations can be stored as a custom Char field (x_additional_affiliations) for reference, or a separate custom relational model can be built to preserve the N:N structure. This decision must be made before migration and documented in the mapping plan.

WealthEngine screening workflows and API-triggered enrichment cannot migrate to Odoo automated actions

WealthEngine's core value is in automated screening triggers — real-time enrichment when a contact enters the system, batch screening on upload, and threshold-based alerts (e.g., flag a donor when P2G crosses a certain score). These are defined as workflow logic inside WealthEngine and have no equivalent in the exported data payload. FlitStack migrates the enrichment data (scores, ratings, asset values) as static fields on the partner record, but the triggering logic must be rebuilt as Odoo automated actions and server actions post-migration. We provide a rebuild reference document listing each WealthEngine workflow trigger and its Odoo equivalent.

Odoo XML-RPC API rate limits differ from WealthEngine's API model — batch sizing matters

WealthEngine API supports up to 600 calls per minute with session-key authentication. Odoo XML-RPC on xmlrpc/2/object has no formally documented per-minute rate limit but performance depends on Odoo server configuration and PostgreSQL query throughput. For large WealthEngine exports (50,000+ profiles with 30+ custom fields each), migration batch sizing must be tuned to avoid Odoo worker timeouts. FlitStack uses configurable batch sizes (typically 200–500 records per commit) and tracks API response times to auto-throttle if Odoo returns 504 errors. Community edition deployments on shared hosting may encounter stricter throttling than dedicated Odoo.sh instances.

Currency and monetary field precision must match between WealthEngine export and Odoo company configuration

WealthEngine stores asset valuations and giving estimates in USD by default, but organizations may have configured WealthEngine to use alternative currencies for international prospects. Odoo monetary fields (x_total_assets, x_cash_on_hand, etc.) inherit the company's configured currency from res.company. If WealthEngine exports contain multi-currency amounts and Odoo's company is set to a single currency, amounts may display incorrectly. FlitStack validates currency fields during the sample migration phase and flags mismatches — the recommended fix is to set Odoo company currency to USD if the majority of WealthEngine data is USD-denominated, and store original currency codes in a companion Char field.