Migrate from Empire SUITE to Odoo CRM

Empire Suite contacts map to Odoo res.partner records with type='contact'. The primary company association is resolved via the partner_id relation after the company partner record is created, ensuring the parent link is in place before the contact lands. Names, emails, phone numbers, street addresses, city, state, and country fields map directly field-for-field, preserving original data without transformation.

Empire Suite companies map to Odoo res.partner records with type='company'. Odoo differentiates companies from contacts using the is_company flag rather than a separate model. Parent‑company hierarchies present in Empire Suite are translated to the parent_id field on the Odoo partner, preserving multi‑level corporate structures and allowing related contacts to attach to the correct parent company.

Empire Suite deals become Odoo crm.lead records with type set to 'opportunity'. Stage mapping follows a value‑by‑value translation against Odoo's crm.stage pick‑list for each sales team, ensuring the named stages and their sequence order are reproduced exactly. The probability field is re‑applied using the stage‑level default unless custom probability values were defined in Empire Suite.

Empire Suite pipelines map to Odoo sales teams (crm.team). Each pipeline's stages become crm.stage records scoped to that team via the team_id reference, preserving the original stage names, sequence order, and any on‑change behavior defined in Empire Suite. This ensures deals land in the correct kanban view with the right column layout when migrated.

Empire Suite projects are migrated to Odoo project.project records. Fields such as project name, description, start and end dates, the associated customer (partner_id), and the project manager (user_id) are transferred directly. The project status or stage in Empire Suite maps to the Odoo stage_id pick‑list, allowing the original progress states to be represented in the new system.

Empire Suite task or sub‑project records become Odoo project.task entries linked to their parent project.project via the project_id field. The task name, planned hours, current stage, and assigned user are mapped field‑for‑field, while parent‑task relationships are preserved using the parent_id reference, ensuring the original work breakdown hierarchy is retained in Odoo.

Empire Suite time entries become Odoo account.analytic.line records linked to the project.project and project.task. The employee (user_id), date, duration/hours, and billable flag are mapped. Billable time entries connect to sale.order.line via the so_line field when Odoo's Timesheets app is active.

Empire Suite notes migrate as Odoo mail.message records with message_type='comment' and no subtype, giving them the same visibility in the Odoo chatter thread as activity logs. Notes are attached to the parent res.partner, crm.lead, or project.task by model and res_id.

Empire Suite file attachments are re-uploaded to Odoo's ir.attachment model, linked to the corresponding res_model and res_id on the parent record. Inline images in notes are downloaded, re-hosted in Odoo's filestore, and the URL is replaced in the note body.

Empire Suite owner IDs are resolved by matching the email address against Odoo's res.users table. Before migration runs, any owners without a matching Odoo user are flagged in the migration report; you can either invite them to Odoo, map them to a fallback user, or hold their records for manual reassignment after go‑live.

Empire Suite custom entities map to Odoo res.partner if the entity represents a person or organization. If the custom entity is transactional (e.g., a deliverables tracker), FlitStack creates a dedicated Odoo model and generates the corresponding Python class and XML view structure in the migration plan.

Each Empire Suite custom contact property becomes an Odoo ir.model.fields record on res.partner. Field type is inferred from the source data type: text values become char or text, dates become date, numeric pick-lists become selection. The custom field name is preserved in the field label and stored as a x_ prefixed db_column.

Deal and project custom fields map to Odoo ir.model.fields on crm.lead and project.project respectively. Value-mapping is applied where the custom field uses a pick-list: each distinct Empire Suite pick-list value gets a corresponding Odoo selection option created in the same order.

Empire Suite workflow rules, approval chains, and automated notifications do not have a direct Odoo equivalent. FlitStack documents every active workflow rule with its trigger condition and action sequence so your Odoo administrator can rebuild it using Odoo's Studio automation builder or Python server actions.

Empire Suite reports and dashboards are not migrated. Underlying data (deals, projects, time entries) migrates completely, so Odoo's native reporting and custom Spreadsheet reports can reconstruct the metrics. FlitStack provides a data dictionary of the migrated tables for use in Odoo reporting setup.