Migrate from Salescamp CRM to Microsoft Dynamics 365 Sales

Salescamp Leads map to either Dynamics 365 Contact (if the lead is qualified and has an associated Company) or Lead (if the lead is new or unqualified). We apply a qualification rule during scoping based on whether the Salescamp Lead has a deal associated or a status indicating active pursuit. The original Salescamp Lead status maps to a custom field sc_original_status__c on the destination record for audit. Multi-Collection membership on a single Lead creates duplicate candidate records that we reconcile by email dedupe before insert.

Salescamp Company records map directly to Dynamics 365 Account. The Company name becomes Account Name, and any associated website or industry data maps to standard Account fields. If a Salescamp Lead has multiple associated Companies, we attach the primary Company as Account and flag secondary associations for the customer's admin to handle manually post-migration.

Salescamp Collections have no direct Dynamics 365 equivalent. We map Collections to Teams in Dynamics 365 by creating a Team per Collection and linking Lead and Contact records to the appropriate Team via TeamMembership. The customer configures Dynamics 365 security roles during setup; we document the Collection-to-Role mapping as part of the handoff and the admin assigns the mapping.

Salescamp Deals map to Dynamics 365 Opportunity. The pipeline stage in Salescamp maps to the Opportunity StageName. We create a corresponding Sales Process and Record Type in Dynamics 365 before migration so that stage values are whitelisted and probability percentages are pre-configured. Closed-won and closed-lost reasons from Salescamp custom fields become Opportunity custom fields in Dynamics.

Salescamp call logs map to Dynamics 365 Task with TaskSubtype = Call. We extract call duration, disposition, and timestamp from the CSV export and map them to Task fields or custom Task fields on the Dataverse table. If the call log CSV does not include engagement content (recording URL, notes), we note the gap and recommend the admin review call records post-migration.

Salescamp SMS logs have no native Dynamics 365 equivalent. We map SMS content to Note records attached to the parent Contact or Lead, with the original timestamp preserved. Alternatively, if the customer uses Microsoft Dynamics 365 Sales Premium or a telephony add-on, SMS logs can be mapped to a custom activity entity; we document both options during scoping and the customer chooses the approach.

Salescamp email sync logs map to Dynamics 365 EmailMessage records linked to an Activity Task. The EmailMessage carries the message body; the Task entry carries the activity timeline marker with the original timestamp. We resolve the WhoId (Contact or Lead) and WhatId (Opportunity or Account) from the Salescamp CSV during the transform phase.

Salescamp Owners map to Dynamics 365 User records by email match. We extract all distinct owner references from Leads, Deals, and Activities and resolve against the destination org's User table. Any Owner without a matching Dynamics User goes to a reconciliation queue for the admin to provision before record import resumes.

Salescamp custom fields per object (Lead, Company, Deal) map to custom fields on the corresponding Dynamics 365 entity. Field type mapping is validated during scoping: picklists become option sets, dates become datetime fields, text fields become nvarchar. Boolean fields map directly. We pre-create the destination custom field schema before any data import using the Dataverse Web API.