Migrate from GENIEE to Odoo CRM

GENIEE SFA/CRM Contacts map to Odoo Lead (for unqualified prospects) or Contact (for qualified records). We analyze the GENIEE contact record's stage, owner assignment, and deal association to determine the split. Contacts with no linked Deals and no recent engagement activity route to Odoo Lead; Contacts linked to active Deals or with recent communication history route to Odoo Contact attached to an Account. The original GENIEE contact ID is preserved in a custom field for audit tracing.

GENIEE Companies map directly to Odoo Accounts. The company name becomes the Account name, and the GENIEE account ID is preserved in a custom field. We map the account hierarchy (parent-company relationships where present in GENIEE) to Odoo's commercial entity and contact links. Japanese regional conventions for department and location data on accounts are normalized to Odoo's address standard format.

GENIEE Deals map to Odoo Opportunities. The GENIEE pipeline stage name maps to an Odoo stage in the configured sales team pipeline. Win/loss probability values from GENIEE migrate to Odoo stage probability percentages. Closed-won and closed-lost reasons from GENIEE custom fields migrate to Odoo lost reason or a custom Char field on the Opportunity. We preserve the full stage history timestamp from GENIEE in Odoo Opportunity log records.

GENIEE deal pipelines (configurable per tenant) map to Odoo Sales Teams. Each pipeline's stages are recreated as Odoo stage records within the corresponding sales team. Stage order and probability mapping follow the GENIEE configuration as closely as Odoo's stage model permits. Odoo's Kanban view maps directly to the GENIEE pipeline visualization paradigm.

GENIEE SFA/CRM Users (record owners) map to Odoo Users by email address. We extract the full owner roster from GENIEE during scoping and provision Odoo Users for each. GENIEE role-based access levels are noted for the customer's Odoo admin to configure via Odoo's access rights model (Technical Settings > Users and Companies). Users without a resolvable email are flagged in the reconciliation report.

GENIEE MA Campaigns map to Odoo Campaigns. Campaign attribution data (UTM parameters, source, medium) stored per Contact in GENIEE is preserved as Odoo Campaign UTM fields (UTM Source, Medium, Campaign) on the linked Lead or Contact. GENIEE campaign targeting parameters and flight dates are noted as a campaign metadata sheet for manual entry into Odoo since these are not standard Odoo Campaign fields.

GENIEE DSP campaigns (budget, targeting parameters, ad formats, flight dates) do not map to any standard Odoo CRM object. We create a custom Odoo model (geniee_dsp_campaign) with fields for DSP budget, targeting_criteria, ad_format, flight_start, flight_end, and status. This model is deployed as a custom module before migration begins. DSP campaign performance metrics (impressions, clicks, bid logs) are exported as separate data files and stored as Odoo attachments linked to the geniee_dsp_campaign record rather than imported as structured fields.

SSP publisher inventory data (slot IDs, floor prices, telco/mobile/desktop classification) is SSP-specific and has no standard CRM equivalent in Odoo. We create a custom model (geniee_publisher_inventory) to hold slot configuration records. The customer decides during scoping whether to activate this model or treat the SSP data as reference-only records archived post-migration. DSP campaign-to-inventory associations are preserved as Many2one links within the custom model.

Attachments on GENIEE Contacts, Accounts, and Deals are exported as binary files and re-uploaded to Odoo via the ir.attachment model. We preserve the original filename, MIME type, and file size. Attachments are linked to the parent Odoo record (res.partner, res.partner, crm.lead, or sale.order) via the res_model and res_id fields. File size limits follow Odoo's ir_attachment_max_size configuration setting.

GENIEE SFA/CRM custom fields vary by tenant. We discover the full custom property list during scoping, generate an Odoo custom field map for each object (Contact, Account, Opportunity), and deploy the fields as Custom Fields via Odoo Studio or direct XML creation before data import. Field types are converted: GENIEE text to Char, integer to Integer, decimal to Float, date to Date, dropdown to Selection, multi-select to Char (comma-separated) or Many2many depending on the customer's preference.

GENIEE tags and labels on Contacts and Companies migrate to Odoo Tags. Tag vocabulary is tenant-defined in GENIEE and is preserved verbatim in Odoo. Odoo applies tags per record type (Contact, Account, Lead) and supports color-coded tag groups. We map tags as lowercase normalized strings to avoid Odoo's case-sensitivity issues on tag matching.

GENIEE engagement records (calls, emails, meetings, tasks) stored in the SFA/CRM subsystem migrate to Odoo Mail Activity records linked to the corresponding Lead, Contact, Account, or Opportunity. Activity type (call, email, meeting, task) maps to Odoo activity_type_id. Activity date, subject, and body text are preserved. The GENIEE engagement sub-type and disposition values migrate as custom Char fields on the Activity record. We resolve the owner assignment using the User mapping from the Users step.