Migrate from Basecamp Scout to Pipedrive

Basecamp Scout People map directly to Pipedrive Persons. The record's name, email, phone, and address fields map to Pipedrive's name, email (as primary key), phone, and address fields. Pipedrive Person records require an email for deduplication; contacts without an email are imported with a placeholder and flagged for review.

Basecamp Scout Companies map to Pipedrive Organizations. Organization name, domain, industry, and address fields translate to Pipedrive's name, website, address fields. Pipedrive's visible_org config controls whether Organizations display in Person records — we set this during migration for consistent visibility.

Basecamp Scout's N:1 person-to-company association (one primary company per person) becomes Pipedrive's org_id lookup on the Person record. If a person had multiple company associations in Basecamp Scout, we preserve the primary and flag the secondary links for manual re-association in Pipedrive's contact-relation model.

Basecamp Scout Deals map to Pipedrive Deals with name, value, close_date, and status fields preserved. Pipedrive requires a pipeline_id on every Deal — we create a default pipeline mirroring Basecamp Scout's deal stages if no pre-existing Pipedrive pipeline matches the source structure.

Basecamp Scout deal status values (active, won, lost, archived) map to Pipedrive stage_id values within the assigned pipeline. We generate a stage-mapping table during discovery; closed-won maps to Pipedrive's closed-won stage and closed-lost maps to closed-lost, with any custom Basecamp Scout stages mapped by name-match.

Basecamp Scout owner IDs are resolved by email match against Pipedrive users. Unmatched owners are flagged before migration; the record is assigned to the migration admin user and the original owner ID is stored in a custom field Basecamp_Scout_Owner_ID__c for audit traceability.

Basecamp Scout's project membership model for contacts on deals translates to Pipedrive's deal_person entries linking a Person to a Deal with a role field. Basecamp Scout's role labels (assignee, reviewer) are preserved as custom role values in Pipedrive's deal_person model.

Basecamp Scout's activity log entries (check-ins, form submissions, time-tagged attendance) map to Pipedrive Activities with type, subject, due_date, and done fields. The original timestamp is preserved as Basecamp_Activity_Date__c custom field since Pipedrive's due_date is the target date, not the original event date.

Basecamp Scout custom fields (dropdown, single-line text, multi-line text, number, date) are created as corresponding Pipedrive custom fields before migration. Pipedrive assigns a 40-character hash key to each custom field — we map the Basecamp Scout field name to the generated key in the field-mapping table so data loads correctly.

Basecamp Scout's geo-tagged attendance records and location proofs have no native Pipedrive equivalent. GPS coordinates, check-in timestamps, and location metadata are preserved as read-only custom text fields on the Person record for audit purposes. Pipedrive's mobile app does not consume geo-data, so this is reference-only.

Basecamp Scout real-time push alerts and notification rules are configuration-level settings, not data records. Pipedrive's Automation builder can replicate trigger conditions (e.g., new Person created, Deal stage changed) with email or task actions, but the specific Basecamp Scout rules must be rebuilt manually. We provide an automation audit export documenting each Basecamp Scout alert rule as a rebuild reference.

Basecamp Scout's hierarchy-based role management (admin, manager, field rep) has no 1:1 equivalent in Pipedrive. Pipedrive's visibility groups and permission sets cover object-level access but not field-force location permissions. We document the Basecamp Scout role structure for your Pipedrive admin to re-implement under Settings > Permissions.

Basecamp Scout digital form submission data is stored as structured records linked to a Person. We import the submission content as an Activity with type='form_submission' and the form field values as a JSON blob in a custom field, preserving all original responses for audit review in Pipedrive.

Basecamp Scout's team productivity reports (individual activity counts, geo-fence breach logs, sales metrics) are aggregated analytics that do not map to Pipedrive's native reporting. We export the report snapshots as CSV attachments linked to the relevant Person or Organization records. Pipedrive's Insights dashboard should be rebuilt for live reporting post-migration.