Migrate from Badger Maps to HubSpot

Badger Account maps directly to HubSpot Company. Address fields (street, city, state, zip, country) map to HubSpot address properties. HubSpot's address property group must be active in the destination portal — we verify this before migration and create the property group if it is missing.

Each Badger Account custom field (Text or Numeric type) becomes a HubSpot custom property on the Company object. Numeric fields map to HubSpot number properties; text fields map to HubSpot single-line text or multiple-line text depending on expected value length. We pre-create all custom properties in HubSpot before writing records so imports land cleanly.

Badger stores geocoordinates per Account record. HubSpot has no native geolocation field type available on standard objects. We map latitude and longitude values to two custom number properties (Badger_Latitude__c, Badger_Longitude__c) on the Company object so the geographic data is preserved for reference or use in third-party map visualization integrations. These properties are created before migration and populated from Badger's account location_data fields.

Badger Contact records (first name, last name, email, phone) map directly to HubSpot Contact. The contact's primary Account in Badger maps to the Contact's associated Company in HubSpot via the association API. Badger allows contacts without a company; these land as unassociated HubSpot Contacts.

Badger assigns each account and contact to a Badger user. We resolve by email match against HubSpot users. Unmatched owners are flagged before migration — your team either creates HubSpot users for them or assigns records to a fallback HubSpot owner. No record lands without an owner.

Badger check-ins with type 'Meeting' map to HubSpot Engagements of type 'meeting'. The original timestamp, associated account and contact references, and free-text comments from the check-in are preserved as HubSpot meeting engagement metadata. These meeting engagements appear in the associated contact's timeline view and are searchable through the HubSpot engagement API for reporting purposes.

Badger check-ins logged as 'Note' map to HubSpot Note engagements on the associated contact or company. The original Badger check-in timestamp is preserved as the engagement timestamp. HubSpot's note format accepts plain text; rich formatting from Badger is converted to plain text to avoid import errors.

Badger Routes are optimized stop sequences with appointment times. HubSpot has no route or sequence-of-visits object. We export route definitions as structured JSON and store them in a HubSpot custom object (Badger_Route__c) with fields for route name, stop order, and account references. Rebuilding the actual optimized sequence requires manual work in HubSpot's workflow or list tools.

Badger territories are map-defined spatial regions. HubSpot has no native territory object. We map Badger territory names to HubSpot Teams (for rep assignment) and store the full territory definition as a structured note in a custom property for admin reference. Actual territory boundaries must be rebuilt using HubSpot's list segmentation or a third-party mapping tool.

Badger user records (name, email, role) resolve to HubSpot users by email address. Active Badger users who have no HubSpot account are flagged as unmatched before migration. Your HubSpot admin creates the user accounts first, or we assign their records to a designated fallback owner during the migration run.

The original Badger account ID is stored as a custom property (Source_System_ID__c) on the HubSpot Company record. This enables delta-run de-duplication if the migration needs to re-run, and gives your team a traceability link back to the source Badger record for reconciliation.

The original Badger contact ID is preserved in a custom property (Source_System_ID__c) on the HubSpot Contact record. This property enables de-duplication logic for any subsequent migration runs and provides a direct reconciliation link back to the source Badger contact for your team to reference during post-migration validation.

Badger's follow-up flag marks accounts needing future attention. HubSpot has no native follow-up flag on standard objects. We map this to a custom checkbox property (Needs_Follow_Up__c) on the Company object so sales reps can filter their queue for accounts awaiting follow-up action, maintaining the original workflow intent from Badger within HubSpot's standard filtering tools.