Migrate your Badger Maps data

Accounts are Badger's primary CRM object. Every Account has a name, address, phone, email, and optional custom fields. We can export all Account fields via CSV (full list or filtered by Visualize tool), import them via spreadsheet, and map them 1:1 to the destination CRM's Account or Company object.

Contacts can be imported via CSV and are associated with Accounts. In CRM integrations, Badger syncs Contacts alongside Accounts. We map Contacts to the destination Contact or Person record and preserve the Account association.

Leads are treated as a separate object in Badger's CRM integration layer, distinct from Accounts. The mapping varies depending on whether the destination CRM has a separate Lead object. Where it does not, we merge Lead records into Contacts and preserve lead-specific fields as custom Contact properties.

Routes are Badger's core scheduling construct: ordered lists of stop locations with appointment times and durations. We can export Routes to PDF and GPX formats. Routes do not exist as standalone records in most CRMs, so we map route metadata (stops, order, timing) to the destination's Activity or Task object.

Check-ins are timestamped visit records linked to an Account, containing the meeting date, time, comments, log type, and meeting notes. We export them via the Reports tab as CSV. Since most CRMs store visits as Activities or Tasks, we map Check-ins to the equivalent activity object and preserve all metadata fields.

Badger supports Text and Numeric custom fields per Account. These are created in Settings > Manage Fields and appear in Account Details. We map custom fields to destination custom properties, applying the correct data type and handling any naming differences between systems.

Visualize filters are UI-layer configurations for colorizing and filtering Accounts on the map. They are not stored as independent data objects. We do not migrate filter configurations as they are tied to Badger's interface and would not apply in a different platform.

Team Members are user accounts within Badger tied to the subscription. Route assignments and territory visibility are managed at the team level. We map team members to users in the destination CRM, preserving territory assignments where possible.

Territory assignment in Badger is implicit through which Accounts are visible to which rep. There is no explicit Territory object. We reconstruct territory boundaries by exporting the account list filtered by the relevant rep and mapping those groupings to the destination CRM's territory or ownership model.