Migrate from Unanet CRM by Cosential to Odoo CRM

Personnel records require a two-pass import to resolve company_id on contacts

Unanet's Company → Personnel → Contact structure means a Contact in Unanet may belong to a Personnel record, which belongs to a Company. In Odoo, contacts have a direct company_id link — there is no Personnel intermediary. FlitStack resolves Personnel → Company first, writing the res.partner company record, then imports Personnel as contacts with company_id set, then imports Contacts that are not Personnel. If your Unanet data has contacts at both the Personnel level and the direct Company level, the import order matters: importing contacts before their parent company is written results in orphaned records with a null company_id. We flag any such dependency chains before committing the import order and surface them in the pre-migration plan.

Custom fields in Odoo Community require developer mode or a custom module manifest

Unanet custom properties are schema-flexible and stored as key-value pairs per object. Odoo's custom field model requires a custom module (with an __manifest__.py) to persist field definitions in a way that survives version upgrades. FlitStack creates a lightweight custom module (flitstack_cosential_import) with ir.model.fields declarations for each custom property discovered in your Unanet export. If you are on Odoo Community without access to a developer, this module must be installed by a user with technical (developer) access. Enterprise edition users can create fields directly in Settings > Technical > Database Structure > Fields without a module, but the field definitions still require admin-level access. We document every custom field created so your Odoo admin can audit them post-migration.

Unanet's proposal automation has no Odoo equivalent and must be rebuilt

Unanet's Publisher module is a core differentiator for AEC firms — it auto-populates Word and PDF proposals from CRM fields (project history, personnel qualifications, resumes, project profiles). Odoo has no native proposal-from-CRM-population feature. Quotations in Odoo (sale.order) pull from the product catalog, not from CRM relationship data. FlitStack migrates all proposal-attached data (contacts, companies, opportunity fields) to Odoo fields, but the Publisher template logic — including conditional field insertion, document layout, and digital signature routing — must be rebuilt using Odoo's template engine (mail.template) or a third-party document automation tool. We export your Unanet Publisher templates as a PDF reference package for your Odoo admin to rebuild.

Odoo pipeline stages are scoped by team; Unanet pipelines are global

In Unanet, a pipeline's stages are global within the account — any user can assign any stage from any pipeline to an opportunity. In Odoo, crm.stage records are scoped to a crm.team. If you have multiple pipelines in Unanet that share a stage name (e.g., 'Qualification' exists in Pipeline A and Pipeline B), those become separate stage records in Odoo, each scoped to a different team. When a crm.lead is imported, its stage_id must correspond to the team_id set on the lead. Mismatched team/stage combinations cause the lead to appear in the wrong pipeline view in Odoo's Kanban. FlitStack builds a stage-mapping table per team before import and validates team_id + stage_id consistency for every opportunity row.

Compass API requires basic-auth credentials that must be sourced from Unanet support

Unanet's Compass API uses basic access authentication (username/password) plus two required headers: x-compass-firm-id and x-compass-api-key. The API key is not visible in the Unanet UI — it must be requested from Unanet support or your account manager. The firm access code (x-compass-firm-id) likewise comes from account provisioning. If either credential is unavailable or the API agreement has lapsed, the migration must fall back to Unanet's CSV export feature (available per-module from the UI), which does not capture all fields or relationship data. We recommend requesting API credentials at the start of the project. If API access is not available, FlitStack documents which fields fall back to CSV export and which relationships require post-migration manual reconciliation.