Migrate from Basecamp Scout to Microsoft Dynamics 365 Sales

Basecamp Scout People map 1:1 to Dynamics 365 Contacts. The email field serves as the unique identifier for owner resolution — Basecamp owner email is matched against Dynamics User.emailaddress1 to assign OwnerId. Phone, job title, and address fields map directly to Contact.Phone, Contact.JobTitle, and Contact.Address fields.

Basecamp Scout Companies map to Dynamics Accounts. Company name maps to Account.Name, website maps to Account.WebsiteURL, and phone maps to Account.Telephone1. Parent-company hierarchies in Basecamp Scout map to Account.ParentAccountId — circular references are flagged before migration. If a parent company does not exist in Dynamics, a placeholder Account is created and linked, with duplicate detection based on name and website.

People records in Basecamp Scout without an existing Account association are evaluated for Lead creation in Dynamics 365 Sales. If the Person record contains only minimal contact data (name + email, no company), they land as Dynamics Leads rather than Contacts, triggering the lead qualification Business Process Flow.

Basecamp Scout To-dos linked to a Company do not map to Opportunities directly. We construct Opportunities by grouping completed To-dos by Company, extracting To-do names as Opportunity.Name, and deriving estimated revenue from any amount field or pricing metadata. Stage defaults to Closed Won; close date uses the To-do's last completion timestamp.

Basecamp Scout To-dos map to Dynamics Tasks. To-do name maps to Task.Subject, description maps to Task.Description, due date maps to Task.ScheduledEnd, and completion status maps to Task.StateCode (Open = 0, Completed = 5). Assigned Basecamp user resolves to Task.OwnerId by email match.

Basecamp Scout Messages map to Dynamics Notes (Annotation entity). Message body maps to Annotation.NoteText, author name maps to Annotation.Subject, and creation timestamp maps to Annotation.CreatedOn. Parent record links preserve the source Project or Person context via Annotation.ObjectId. If multiple messages reference the same parent, they are attached sequentially, preserving chronological order. Attachments embedded in messages are stored as separate Note attachments, linked by Annotation.ObjectId and Annotation.Id.

Basecamp Scout Projects have no direct Dynamics equivalent. We map Projects to Accounts with a Project_Name__c custom field and store project-specific metadata (start date, client type) as additional custom fields on the Account. If your team uses multiple projects per client, we surface them as related Account records with a Project_Link__c field.

Basecamp Scout custom fields of type Dropdown (up to 100 options) map to Dynamics 365 Option Sets. We extract the full option list from the Basecamp Inbox field definition, create a corresponding Option Set in Dynamics, and map each option label to an integer Option value with the original label preserved in Option Set labels.

Basecamp Scout numeric custom fields map to Dynamics custom columns (new_numberfield). We evaluate field precision — integer values use Whole Number type, decimal amounts use Decimal Number type. Required-flagged fields in Basecamp Scout become Required fields in Dynamics. Empty numeric values become null in Dynamics; if data exceeds Whole Number limits, the column type upgrades to Decimal Number automatically.

Basecamp Scout date custom fields map to Dynamics Date Only columns. Timezone handling follows Basecamp's company-level timezone setting — we store dates in UTC in Dynamics but preserve the original timezone in a CreatedFrom_Timezone__c custom field for audit continuity. If a date field includes time information, the time portion is stripped and stored separately in a CreatedFrom_Time__c field, ensuring no data loss during migration.

Basecamp Scout file attachments re-upload to Dynamics 365's SharePoint-integrated document storage. The Attachment record's URL, filename, and size migrate to a SharePoint Document Location linked to the parent Account or Contact record. Files exceeding Dynamics' 50MB limit are flagged for manual retrieval.

Basecamp Scout's Hill Charts visualize work momentum by showing where tasks sit on a hill from 'starting' to 'finishing.' Dynamics 365 Sales has no native equivalent — the concept does not map to Opportunities or Activities. We export Hill Chart data as a structured JSON file for reference and manual entry into Dynamics dashboards if needed.

Basecamp Scout's automatic check-ins (time-tagged attendance, geo-fence logs, location snapshots) have no Dynamics 365 equivalent. Geo-attendance records migrate as rows in a custom CheckinHistory__c table linked to the Contact record, with latitude, longitude, timestamp, and check-in type preserved. If the Dynamics license does not include custom tables, FlitStack exports the check-in data to CSV, allowing manual import via Power Automate later.