Migrate from Termene to Odoo CRM

Termene company records map directly to Odoo res.partner records. The partner is created as a company-type partner (is_company=True) so child contact records can be attached. Name, address, and registration fields map directly. This direct mapping preserves the original Termene identifiers and ensures downstream reports can reference the same company across both systems.

When Termene provides contact-level data (person name alongside company), we create a child res.partner record linked via parent_id to the company partner. Email and phone attach to the contact; company fiscal data stays on the parent. The child contact inherits the company’s address unless a specific location is provided in the Termene data.

Romanian company fiscal identifier (CUI) migrates to Odoo's VAT field on the partner record. Odoo validates VAT format using Romanian localization rules when the l10n_ro module is installed. If l10n_ro is not present, the VAT field remains editable without validation, and the CUI value is stored as a plain string.

Company registration number (ONRC) maps to the Odoo ref field. The ref field is free-form and used by Romanian implementations to store ONRC registration numbers alongside VAT. This allows finance and compliance teams to reference the official registry entry directly from the partner form, streamlining audit processes.

Termene financial metrics (annual revenue in RON) have no native Odoo equivalent. We create a custom float field x_annual_revenue on res.partner and store the Termene value for reference by the sales team. The field appears on the partner’s form and can be included in Odoo reports for revenue-based segmentation.

Employee count from Termene migrates to a custom integer field x_employee_count on res.partner. Used for segmentation and territory planning in Odoo. This metric enables managers to prioritize outreach based on company size, allocate resources efficiently across regions, and build dynamic groups within Odoo’s reporting tools.

Termene debt flags (whether a company has reported debts) map to x_has_debts boolean on res.partner. The flag surfaces in Odoo's partner list view for risk-aware selling. Sales reps can filter the partner list to display only high-risk accounts, enabling proactive follow-up and informed pricing decisions.

Payment delay indicators from Termene (e.g., 'intarzieri 30-90 zile') migrate to x_payment_status char field. Stores the last reported payment behavior from Termene's registry. This information helps the collections team prioritize outreach, and it can be used in Odoo’s automated actions to trigger reminders when payment delays exceed defined thresholds.

Termene active/inactive company status maps to Odoo's active boolean. Inactive companies in Termene can be archived in Odoo (active=False) rather than deleted, preserving historical record. Archived partners remain visible in historical quotations, invoices, and lead reports, ensuring data continuity and supporting compliance audits.

Company website from Termene maps directly to Odoo's website field on the partner. Odoo uses this for lead enrichment and website tracking integration. With the website field populated, the CRM can automatically pull company details from Odoo’s built-in website visitor analytics, enhancing lead scoring and personalization.

Street, city, state, zip, country map to Odoo's address fields on partner. When Termene provides county (judet), we map it to state_id using Romanian localization if l10n_ro is configured. If l10n_ro is absent, the county value can be stored in a custom char field to preserve the geographic detail for reference.

Termene tracking identifier or source tag (e.g., 'termene_monitor') is stored in x_data_source char field on res.partner to indicate the record originated from Termene rather than inbound. This field is useful for filtering reports to show only Termene-sourced partners, and it can be used in Odoo’s workflow rules to apply specific routing or tag assignments.