Migrate from Briostack to Odoo CRM

Briostack Customer records map to Odoo crm_lead with type='lead' by default. The is_customer flag from Briostack migrates as a custom Boolean field (x_is_customer) on the crm_lead. When a Customer record has no associated Company in Briostack, the resulting crm_lead is created without a partner_id and must be assigned manually in Odoo post-migration, or linked to a default partner record.

Briostack Company maps to Odoo res_partner with is_company=True. Parent-child company hierarchies in Briostack use the parent_company_id field and map directly to Odoo's parent_id on res_partner. Each Company in Briostack must be migrated before Customer records that reference it, to ensure parent_id resolution succeeds during the load phase.

Briostack Customers linked to a Company map to Odoo res_partner with is_company=False and partner_share=True, linked to the parent Company record via parent_id. When a Customer has multiple Company associations in Briostack (N:N model) only the primary company is set as parent_id; secondary associations are stored as partner relations in Odoo.

Briostack Deal maps to Odoo crm_lead with type='opportunity'. The deal stage name maps to the corresponding stage_id in the target Odoo sales team. Probability values are mapped directly if Briostack provides them; otherwise Odoo's stage-based probability is applied per the stage configuration.

Briostack Service Calls and Appointments have no standard Odoo CRM equivalent. Scheduled calls map to mail_activity records with activity_type_id matching the Odoo standard. Completed service records with pest-type, chemical-used, and resolution notes are stored as custom fields on the crm_lead and as PDF attachments.

Briostack Call, Email, Meeting, and Note activity records map to Odoo mail_activity entries linked to the parent crm_lead. The activity_type_id field is set per interaction type to match Odoo's standard activity types. Original timestamps (activity_date) and owner_id are preserved during migration. Note body content migrates to mail_message or ir_attachment depending on whether files are attached.

Briostack custom fields on any standard object require manual creation in Odoo before the migration loads. FlitStack delivers a custom-field manifest listing field name, type, and Briostack value options so your Odoo admin creates them in Settings > Technical > Custom Fields. Field labels, help text, and pick-list values are documented in the migration plan.

Briostack custom objects (Enterprise tier) require an equivalent Odoo model to be defined via XML data file or Odoo Studio. Custom object records are migrated after the model and fields exist in Odoo. N:N associations between Briostack custom objects need Odoo many-to-many relational fields defined upfront.

Briostack Technician and Staff records map to Odoo res_users. Owner-assignment fields on Briostack records resolve to Odoo users by email match. Unmatched owners are flagged before migration; your team either invites them to Odoo first or assigns to a fallback user.

Briostack route definitions and route-to-technician assignments have no standard Odoo CRM equivalent. These are preserved as documentation attachments and custom fields on the crm_lead for reference. Rebuilding route planning in Odoo requires the Odoo Field Service module or a third-party routing integration.

Briostack marketing campaigns and automation sequences do not migrate. Odoo Email Marketing (mass_mailing module) handles email campaigns but must be configured from scratch. FlitStack exports Briostack campaign definitions as a reference document for your Odoo admin or marketing team to rebuild.