Migrate from Badger Maps to Pipedrive

Badger accounts map directly to Pipedrive organizations. Organization name, address, phone, website, and industry field transfer as-is. Multi-address accounts in Badger require selecting a primary address for the organization record; secondary locations surface as a note or custom field on the Pipedrive organization.

Badger people (contacts) linked to accounts map to Pipedrive persons with the organization link preserved. Email, phone, job title, and owner assignment transfer directly. Badger's primary contact flag becomes a custom field or note on the Pipedrive person record. The primary contact flag is stored as a boolean custom field or appended to the person notes for quick identification.

Badger check-ins — logged visits with timestamp, account link, and notes — become Pipedrive activities of type 'meeting'. Original check-in time becomes the activity due date and start time; the linked Badger account becomes the linked organization. Notes from the check-in migrate as the activity's notes field.

Check-ins that contain only comments and meeting notes without a scheduled time become Pipedrive note activities. The account link is preserved as the organization association. We flag check-ins with no timestamp for manual review before migration. Any such entries are logged in a pre-migration audit report, and your team confirms whether to include or exclude them from the migration run.

Badger follow-up markers map to Pipedrive tasks with the linked organization or person. Due date and priority transfer from the follow-up's schedule. Uncompleted follow-ups at migration time land as open tasks in Pipedrive. Completed follow-ups are imported with a 'done' flag set, preserving the completion status from Badger.

Badger routes (stop sequences, optimization data, GPS tracks) are a routing construct with no Pipedrive equivalent. We preserve route names as a text custom field on the linked organization for reference. Territory and routing strategy must be re-established in Pipedrive or a third-party routing tool post-migration.

Badger text custom fields on accounts — such as Specialty, Priority, or custom flags — map to Pipedrive organization custom fields of type 'text'. Field name and values transfer verbatim. Pipedrive generates a hash key for each custom field; we map by field name and re-create on the destination.

Badger numeric custom fields — like Sales YTD, visit count, or custom scoring — map to Pipedrive organization custom fields of type 'numeric'. Zero-value handling matches source (Badger may store zero vs. null differently; we normalize to zero or blank based on your preference).

Badger owner IDs resolve by email match to Pipedrive users. Unmatched owners are flagged before migration — your Pipedrive admin either invites them first or reassigns to a fallback user. No record lands without a Pipedrive owner. We generate a pre-migration owner report listing any unmatched email addresses for immediate action.

Badger's optional Lead object — synced from the integrated CRM — maps to Pipedrive's Lead feature if enabled on your plan. Lead status and custom lead fields transfer. Pipedrive Leads inherit deal custom fields, so mapping from Badger's lead data requires verifying the Lead feature is active.

Badger's product catalog entries (synced from the CRM) map to Pipedrive products if present. Product name, price, and unit transfer directly. Bundle and multi-product configurations require manual review post-migration. If your Badger data includes product images or descriptions, they can be attached as file notes in Pipedrive, provided storage limits are observed.

Files attached to Badger accounts (images, PDFs, spreadsheets) are re-uploaded as Pipedrive file attachments linked to the corresponding organization or person record. Pipedrive storage limits apply per plan — Essential includes 5GB/user; larger imports may require archival or plan upgrade.

Badger territory assignments do not map to a native Pipedrive object. We migrate territory names as a custom field or tag on the organization. Rebuilding territory-based routing logic requires Pipedrive's territory configuration or a third-party routing integration. Your team can use these tags to assign reps or build custom reports in Pipedrive.