Migrate from Basecamp Scout to HubSpot

Basecamp Scout users map to HubSpot owners by email match. The owner name, title, and admin flag from Basecamp Scout carry into HubSpot user profile fields. Unmatched Basecamp Scout users are flagged before migration so your HubSpot admin can invite them or assign a fallback owner.

Basecamp Scout leads with no associated company map directly to HubSpot Contacts. The lifecycle_stage is set to 'lead' by default for all migrated leads unless a workflow rule in HubSpot updates it based on subsequent activity. Original lead create date is preserved as a custom datetime property.

Basecamp Scout contacts map 1:1 to HubSpot Contacts. Name, email, phone, job title, and address fields translate directly. HubSpot's contact model supports multiple companies per contact through contact-to-company associations, which Basecamp Scout supports natively as well. Custom properties attached to the Basecamp Scout contact record also migrate as HubSpot custom properties, preserving any additional data your team collected.

Basecamp Scout company records map to HubSpot Companies. Name, domain/website, industry, employee count, and annual revenue fields translate directly. Parent-child company hierarchies in Basecamp Scout map to HubSpot's Parent Company field, maintaining organizational structure. All company-associated contacts retain their links during migration, ensuring relationship continuity across both platforms.

Basecamp Scout visit logs and geo-tagged check-in entries become HubSpot Meeting activities with a timestamp equal to the original visit time, plus a Note entry capturing the geo-tag coordinates, proof-of-visit text, and any attached images. This preserves the field activity context in HubSpot's activity timeline.

Basecamp Scout tasks with a due date and assignment map to HubSpot Tasks. The task subject, due date, completion status, and assigned user (via email match) carry into HubSpot. Open tasks migrate as open tasks; completed tasks preserve the completed timestamp.

Basecamp Scout's geo-tagged proof-of-visit entries — including the GPS coordinates, timestamp, and any accompanying text or photos — are stored as HubSpot Notes with the location data in the note body. Attachments re-upload to HubSpot Files and link to the associated contact or company record.

Form submissions in Basecamp Scout that capture contact information map to HubSpot Contacts with the form name stored in the original_source_drill_down_1 property or a custom property. Submission timestamps are preserved. The contact is created or updated based on email match against existing HubSpot contacts.

Basecamp Scout's pre-built reports (attendance, team productivity, geo-fence compliance) have no direct HubSpot equivalent. If your team relies on these reports, we map the underlying data to a HubSpot Custom Object so the data is preserved for reference, and we document the HubSpot-native alternative (HubSpot dashboards or a BI integration) for rebuilding.

Basecamp Scout dropdown custom fields with defined option lists map to HubSpot dropdown custom properties with the same option labels. Value-by-value mapping is applied for each option label so the pick-list semantics are preserved in HubSpot reporting and workflow filters.

Basecamp Scout numeric custom fields map to HubSpot number custom properties. The field name and numeric value transfer directly. No transformation is applied since both platforms support floating-point numeric storage. Decimal precision and number formatting are preserved during the migration. If Basecamp Scout stores integers only, they migrate as integer properties in HubSpot. Any validation rules or conditional formatting defined in Basecamp Scout are documented for manual recreation in HubSpot.

Basecamp Scout date custom fields map to HubSpot date custom properties. The original date value transfers directly. Timezone handling follows HubSpot's company-level timezone setting configured in your HubSpot portal. Date-only fields preserve just the date portion, while datetime fields maintain both date and time information. All date values retain their original timestamps during migration. HubSpot's timezone configuration determines UI display without altering the underlying values.