Migrate from Badger Maps to Salesforce Sales Cloud

Badger Accounts map 1:1 to Salesforce Accounts. The primary Account fields (name, address, phone, website) map directly. Badger's category/tag fields map to Salesforce custom pick-list or text fields on Account. Parent account hierarchy in Badger maps to Salesforce ParentId if present.

Badger Contacts map to Salesforce Contacts when the record has an associated Account. If a Badger Contact has no company association, Salesforce requires an AccountId — we attach it to a default 'Unassigned' Account or create one placeholder Account per orphaned contact.

Badger Contacts that have no primary Account AND are marked as prospects route to Salesforce Lead. The LastName field pulls from Badger's contact name; email, phone, and title map directly. If the contact has an email but no company, Lead conversion is recommended post-migration.

Badger check-ins map to Salesforce Tasks with Type='Check-in'. The WhatId links to the parent Account record. Original Badger check-in timestamp maps to ActivityDate. GPS coordinates from Badger's location data are stored in custom Latitude__c and Longitude__c fields on the Task record.

Badger check-ins with log type 'Meeting' map to Salesforce Events with the original start/end time preserved. WhatId links to the Account. Meeting notes from Badger map to Event Description. Duration defaults to 30 minutes if Badger's appointment length is not set.

Badger notes attached to Accounts or Contacts map to Salesforce Notes (modern Notes object, not the legacy Note). Original timestamps and the parent record link are preserved. Rich-text formatting in Badger notes is converted to Salesforce's note format, preserving bold, italic, and bullet points where possible.

Badger territory assignments stored as a property on Account have no native Salesforce equivalent without Territory Management. We map them to a custom pick-list field (Territory__c) on Account. If Salesforce Territory Management is active in the destination org, we generate a mapping plan to populate the Territory object instead.

Badger Route objects (ordered stop sequences) have no Salesforce equivalent. We create a Route__c custom object with a parent AccountId, route name, and optimization date. Child Route_Stop__c records hold each stop's AccountId, sequence order, scheduled time, and GPX waypoints as a custom text field.

Badger custom fields created in Settings > Manage Fields map to Salesforce custom fields on the equivalent object (Account or Contact). The API name appends __c per Salesforce convention. Text fields up to 255 chars map to Text(255); longer text maps to Long Text Area(131,072). We flag any Badger custom field exceeding Salesforce limits before migration.

Badger numeric custom fields map to Salesforce Number fields on Account or Contact. Decimal precision and scale are inferred from the Badger field's stored values. We validate that Salesforce field-level security profiles include the migrated numeric fields for the correct user roles.

Badger owner assignments on Accounts and Contacts are resolved by email match against Salesforce Users. If a Badger owner email has no matching Salesforce User, the record lands on a designated fallback owner and the unmatched owner email is preserved in a custom Source_Owner_Email__c field for admin review.

Files attached to Badger Accounts or Contacts are downloaded and re-uploaded to Salesforce Files (ContentDocument/ContentVersion model). File size limits apply: Salesforce default 25MB per file. Inline images embedded in Badger notes are extracted and hosted as Salesforce Files linked to the parent record.