Migrate from Basecamp Scout to Salesforce Sales Cloud

Scout people with active status map to Salesforce User records. Owner resolution runs by email match against Salesforce users. Unmatched people are flagged before migration — teams either create Salesforce users first or assign records to a fallback user so no record lands without an OwnerId.

Scout client records map directly to Salesforce Account. Client name becomes Account Name; phone, address, and website fields map field-for-field to the Account's Phone, BillingStreet, BillingCity, BillingState, BillingPostalCode, BillingCountry, and Website. Clients that lack a company name are inserted with a placeholder Account named 'Individual — Scout' to satisfy Salesforce's required Name field and preserve any associated contact or activity data.

Scout client records that represent individual people rather than organizations map to Salesforce Contact with a primary AccountId reference. The Contact's LastName is populated from the client name, while Email, Phone, and Title map directly. The Contact's AccountId points to the previously migrated Account record so Salesforce's standard Contact layout renders correctly with the Account header and related lists.

Scout leads migrate as Salesforce Lead records. Lead status from Scout maps to Salesforce Lead Status pick-list; Scout rating (Hot/Warm/Cold) maps to Salesforce Rating. Original create timestamps are preserved in a custom datetime field since Salesforce sets CreatedDate at migration time.

Scout follow-up records map to Salesforce Task. The follow-up description becomes Task Subject; detailed notes map to Task Description. Task Status defaults to 'Completed' if the Scout follow-up shows a completed state, or 'Not Started' otherwise. OwnerId resolves by email match against Salesforce users.

Scout meeting records map to Salesforce Event with subject, start/end datetime, and location preserved. If Scout records attendee IDs, we resolve each attendee to a Salesforce Contact or Lead and populate EventWhoIds. Original create timestamps preserved in a custom datetime field for reporting continuity.

Scout's geo-tagged attendance records (timestamp + GPS coordinates) have no Salesforce equivalent. We create a custom text field (Attendance_Log__c) on the Task object and store each attendance entry as a JSON payload: timestamp, latitude, longitude, and user reference. Your admin can parse this data into a reporting object post-migration.

Scout stores role assignments (e.g., Field Rep, Team Lead, Manager) on people records. Salesforce User does not have a native role field for this purpose. We create a custom pick-list field (Scout_Role__c) on the User object with values matching Scout's role options. Multi-value role assignments require a custom junction object.

Scout's team assignment field maps to a custom text field (Scout_Team__c) on the User object. Salesforce territories operate at the Account/Lead level, not the user level, so the Scout team name is stored as text for reference and can be used as a filter in list views or reports.

Scout stores latitude and longitude as separate fields (Geo_Latitude and Geo_Longitude) on records. Salesforce's Geolocation compound field consolidates these into Location__c with Location__latitude__s and Location__longitude__s subfields. We create the custom Geolocation field on the target object and populate both subfields from Scout's source values.

Scout digital forms store responses as name-value pairs attached to a record. We create custom fields on the Account or Contact object for each unique form field and populate them from the response data. Multi-select or free-text responses are stored in a custom long-text area if no structure mapping applies.

Scout file attachments on any record re-upload to Salesforce Files (ContentDocument/ContentVersion). Files are linked to the target Salesforce record via ContentDocumentLink. File size limits apply: Salesforce default 25MB per file; files exceeding this are flagged for chunking or alternate storage before migration.