Migrate from Badger Maps to Twenty CRM

Badger Maps accounts map directly to Twenty CRM Companies. The account name becomes Company.Name, the address fields map to address fields on the Company record, and the domain field maps to Website. The companyId generated during Company import is used to link Person records in the next step.

Badger Maps stores one primary contact per account with name, email, phone, and job title. This maps to Twenty's People object. The contact's associated accountId links to the Company record via Twenty's companyId relation. Multiple contacts per account in Badger Maps would require multiple Person records with the same companyId.

Badger Maps custom fields (text or numeric type, set via Settings → Manage Fields) map to Twenty custom fields created in Settings → Data Model before import. Text fields in Badger Maps become TEXT type fields in Twenty; numeric fields become NUMBER type fields. The import order requires custom fields to exist before CSV import runs.

Badger Maps check-in logs contain date, log type (visit, meeting, call), account reference, and free-text comments. These map to Twenty Notes attached to the corresponding Company record. The check-in type becomes the Note title; the comment text becomes the Note body. Original check-in timestamps are preserved in the Note's creation date.

Badger Maps allows filtering accounts by category (e.g., Specialty, business type) set during account creation or via the Visualize filter. These category values map to a Twenty custom pick-list field (e.g., Account_Category__c) on the Company object. Each distinct category value in Badger Maps becomes a pick-list option in Twenty.

Badger Maps territory assignments are stored per account. There is no native territory object in Twenty CRM. We preserve territory assignment as a custom pick-list or text field (Territory__c) on the Company object so sales managers can filter companies by territory post-migration. Territory hierarchy (parent/child territories) is flattened into a single field value.

Badger Maps route names (saved routes containing specific account stops) have no direct equivalent in Twenty CRM. We capture route names as a custom text field (Assigned_Route__c) on the Company record, populated with the last saved route name containing that account at migration time. This preserves routing context for territory planning without a native map view.

Badger Maps rep assignments per account map to Twenty's assigned collaborator field on the Company record. The rep email in Badger Maps is matched against Twenty Workspace Members by email address. Unmatched owners are flagged before migration and assigned to a fallback Workspace Member.

Twenty's CreatedAt timestamp is set at migration time, not inherited from Badger Maps. Original account creation dates from Badger Maps are preserved as a custom datetime field (Original_Create_Date__c) on the Company record for reporting continuity and data-age analysis. This field allows managers to filter companies by account age, build reports on customer tenure, and maintain historical context for long-term relationship tracking across the migration boundary.

The Badger Maps internal account identifier is stored as Source_System_ID__c on the Twenty Company record. This enables delta-run de-duplication on subsequent syncs, audit traceability back to the original record, and matching if a future Badger Maps re-integration is needed. The field also supports reconciliation workflows by allowing your team to cross-reference migrated records against Badger Maps exports using the original identifier.

Badger Maps follow-up reminders flagged per account map to Twenty Tasks attached to the Company record. The reminder text becomes the Task title, and the due date (if set) becomes the Task due date. If no due date is set, the Task is created with an open status for the rep to schedule.

Teams using Badger Maps' Advanced Integration with Salesforce or HubSpot store linked CRM record IDs per account. These cross-system IDs have no functional value in Twenty CRM and are preserved as a read-only text field (Source_CRM_Link__c) for reference only — they do not create live CRM links.