Migrate from Badger Maps to Odoo CRM

Badger accounts map directly to Odoo res.partner records with type='contact'. The account name becomes partner.name, address fields map to street, city, state_id, country_id, and zip. Latitude/longitude from Badger are stored as custom Decimal fields on the partner record since Odoo does not natively store geocoordinates on contacts.

Badger accounts that represent companies map to a parent res.partner with is_company=True. Badger contacts linked to that account map as child res.partner records with parent_id set to the company partner. This reproduces Badger's account-to-contact hierarchy in Odoo's partner structure. The parent-child relationship is preserved so Odoo displays the company and its contacts in a linked hierarchy view, maintaining the organizational context your team built in Badger Maps.

Badger contacts stored as sub-records of an account become res.partner with parent_id pointing to the company partner. Fields including name, email, phone, mobile, and job title map to Odoo's standard contact fields. Badger contact IDs are preserved in a custom Source_ID field for delta-run deduplication.

Badger routes have no Odoo equivalent — Odoo has crm.team for sales teams and tags on partners for segmentation. FlitStack maps Badger route names to a custom Char field (badger_route__c) on the partner, or creates crm.team records named after each route and assigns partners via team_id. Route ordering and optimization logic is not migratable and must be rebuilt in Odoo.

Badger check-in records include timestamp, account link, meeting notes, and GPS coordinates. FlitStack transforms these into Odoo mail.activity records with activity_type_id='meeting' or 'call', date=True, and the Badger check-in notes stored in the activity's note field. Original GPS coordinates stored in custom Decimal fields on the activity record.

Badger category assignments on accounts (e.g., 'Specialty: Cardiology') map to Odoo res.partner.category tags. Each unique Badger category value creates a corresponding Odoo tag. Partners with multiple categories receive all corresponding tags. During migration, FlitStack compiles all unique Badger category values first, then pre-creates matching Odoo tags before inserting partner records so tag assignments resolve correctly on the first pass.

Badger custom Text fields map to Odoo Char fields created on res.partner. Field labels are preserved exactly as they appear in Badger. For multi-value custom fields with delimited data, FlitStack stores the concatenated string in the Char field or converts values into Odoo tags depending on the data pattern identified during audit. Odoo's Char fields support up to 255 characters.

Badger custom Numeric fields map to Odoo Float or Integer fields on res.partner based on the field's original scale and precision. If the Badger field stores whole numbers, FlitStack creates an Integer field; if it contains decimal values, a Float field is used. Badger numeric values with decimal precision are preserved exactly during migration so that any calculations or reporting based on these numbers remains accurate in Odoo.

Badger follow-up dates on accounts migrate as Odoo mail.activity records with date_deadline set to the follow-up date, activity_type_id='meeting', and the partner linked via res_id/res_model. This populates Odoo's 'Activities' tab on each contact. If an account has multiple follow-up dates, each date becomes a separate mail.activity record. The activity appears in the partner's activity stream, allowing reps to track upcoming tasks and managers to view scheduled follow-ups in Odoo's pipeline view.

Badger owner assignments map by email match to Odoo res.users. Unmatched owners are flagged before migration; records are assigned to a fallback Odoo user or left with no user_id and flagged for manual assignment. Odoo's user_id field on partner is the closest equivalent to Badger's per-account owner.

If Badger's lead generation feature produces records, these map to Odoo crm.lead. Name, email, phone, source, and any custom fields translate to crm.lead fields (partner_name for company, contact_name for individual, email_from, phone). Stage defaults to Odoo's first pipeline stage. FlitStack maps Badger lead status values to corresponding Odoo stage names where possible, preserving pipeline context as leads enter the Odoo CRM workflow.

Files attached to Badger accounts (e.g., documents, images) are downloaded and re-uploaded as Odoo ir.attachment records linked to the corresponding partner via res_model='res.partner' and res_id=partner_id. Odoo attachment size limits apply. FlitStack preserves the original filename and file extension during upload. If attachments exceed Odoo's size limit, FlitStack flags these for review and provides guidance on alternative storage such as external document management or cloud storage links within the contact record.