Migrate from Badger Maps to Microsoft Dynamics 365 Sales

Badger Accounts map 1:1 to Dynamics 365 Accounts. Badger stores company name, address, phone, website, and category. Dynamics Account stores these same fields plus industry, employee count, and annual revenue. If Badger Account has no address but is associated with a Contact that does, the Contact address can be promoted to Account address during migration.

Badger Contacts map to Dynamics Contacts with first name, last name, email, phone, mobile phone, job title, and address fields preserved directly. Dynamics requires an Account lookup (AccountId) — Badger Contacts without a primary company get attached to a default 'Unassigned Account' record or your specified fallback account.

Badger Leads that are not yet converted to Accounts or Contacts migrate as Dynamics Leads with full field parity. Dynamics Lead has a Status and Lead Quality Score field that can be populated from Badger lead score data if present. Leads are not converted to Contact/Account during migration — conversion is a Dynamics admin decision post-migration.

Badger text custom fields migrate to Dataverse text columns on the Account, Contact, or Lead table depending on which entity the custom field was defined under. Dynamics sets the Max Length to 4000 characters. If the Badger field was used as a pick-list (text values), we create a Dataverse OptionSet and map values one-by-one.

Badger numeric custom fields migrate to Dataverse Whole Number or Decimal columns depending on the data. Integer values migrate as Whole Number; decimal values migrate as Decimal with appropriate precision. The field inherits the name from Badger and is added to the same entity (Account, Contact, or Lead) where it was defined.

Badger check-ins (timestamped customer visits) migrate as Dataverse Activities. If the check-in has a scheduled time window it becomes an Appointment; if it was a log-only visit it becomes a Task. The Regarding field links to the Account or Contact in Dynamics. Original check-in timestamp, rep owner, and notes are preserved. GPS coordinates from Badger are stored in a custom text field since Dataverse has no native location type.

Badger territory assignments (which rep owns which territory) map to Dynamics Territory records linked to User records. Badger territory name and rep assignment become a Territory record with the rep's UserId. Shape-boundary data (polygon coordinates) cannot migrate because Dynamics has no native geometry storage — your team recreates boundaries in a mapping tool like Maplytics post-migration.

Badger Routes contain ordered stops with optimized sequencing — this is a Badger-native optimization concept with no Dynamics equivalent. We create a custom Route_Stop__c Dataverse table with fields for AccountId, Sequence, Scheduled_Time__c, and Route_Name__c so the ordered stop data is preserved, but Dynamics does not have built-in route visualization. Route optimization logic must be re-established using a Dynamics-compatible mapping add-in.

Badger user accounts (sales reps) are resolved by email match against Dynamics 365 SystemUser records. If a Badger user has no matching Dynamics user, their records are assigned to a fallback owner and flagged for admin review. Reps must have Dynamics licenses assigned before migration for owner resolution to succeed.

Badger follow-up reminders are timestamped tasks linked to an Account or Contact. They migrate as Dataverse Tasks with Subject, Due Date, Priority, and Regarding lookup preserved. Status is set to Not Started on migration unless the follow-up date has passed, in which case it is set to Overdue.

Badger files attached to accounts or contacts migrate as Dataverse Note (Annotation) records. File size limits of 5MB per note apply. If Badger stores files larger than this, they are exported to a designated SharePoint or Blob location and a Note record with the URL is created in Dynamics pointing to the external file.

Badger's integration configuration (which CRM it synced to, sync direction, mapped objects) has no Dynamics equivalent because Dynamics IS the CRM destination. These settings are documented as a pre-migration reference for your admin to configure the Badger-Dynamics integration being decommissioned.