Migrate from Upvise to Odoo CRM

Upvise per-app custom fields require a custom Odoo Python module

Upvise allows custom field creation directly within each app's Options menu, and these fields are stored as metadata tied to that app's schema. Odoo Community edition has no GUI equivalent — custom fields must be declared as ir.model.fields inside a custom Python module using a _inherit = 'model.name' class definition and an XML view override. FlitStack generates the module skeleton during the Odoo schema-prep phase, but the module must be installed in Odoo before the data migration runs. Fields that are not pre-declared will be skipped and flagged in the migration report.

Odoo res.partner is a unified contact-and-company model

Upvise maintains separate Contact and Company objects with N:N associations between them. Odoo uses a single res.partner model where both companies and people are stored as partners — a company is a partner with contact_type='contact', and individual contacts are partners with a parent_id pointing to the company partner. This means every Upvise Company becomes an Odoo res.partner record, and Upvise Contact records linked to that company get a parent_id set to the corresponding Odoo partner. FlitStack handles this during the dependency-ordered migration (companies first, then contacts), but teams should review the parent_id assignments in the sample migration diff before committing to the full run.

Multiple Upvise pipelines split across Odoo sales teams

Upvise supports multiple independent named pipelines, each with its own stage sequence. Odoo CRM uses a single pipeline view with stage values scoped to crm.team. When migrating a multi-pipeline Upvise account, each Upvise pipeline maps to a separate Odoo crm.team, and the pipeline's stage names become crm.stage records within that team's scope. Teams must pre-create the crm.team records in Odoo (or accept FlitStack's setup plan) so stage_id pick-list values are correctly scoped before opportunities are loaded. Without this, Odoo will throw validation errors on stage assignment.

Odoo does not natively preserve external activity history

Upvise logs calls, emails, GPS traces, and form submissions with full timestamps, body content, and owner attribution. Odoo CRM records follow-up activities (logged calls, meetings, emails) created within Odoo, but it does not have a native equivalent to import external activity history from another system. FlitStack migrates Upvise activity records as mail.message entries in Odoo's chatter, preserving the original timestamp, body, and author. However, Odoo's activity-gantt and next-activity features will not display this historical data in their native views — it will appear as chatter comments on the record.

Odoo External API requires Custom Plan (Enterprise edition)

Upvise exposes a full xmlrpc API for reading and writing all standard and custom objects on all plan tiers. Odoo's External API (xmlrpc/2/object and xmlrpc/2/common) requires an active Odoo subscription on the Custom Plan tier — Community edition and Standard plan users cannot access the API externally. If your target Odoo instance is on Community or Standard, FlitStack can load data via Odoo's CSV import interface instead, which requires additional preparation for relational fields. This must be clarified before the migration scope is confirmed.