Migrate from SalesTown CRM to Microsoft Dynamics 365 Sales

SalesTown CRM Leads map directly to Dynamics 365 Sales Lead. The Lead Management System (LMS) association in SalesTown becomes a custom text field or lookup in Dynamics 365 if the destination org tracks LMS reference. We preserve lead score, status, source, and owner assignment during import. The lead record is loaded before Contact to maintain the Lead-to-Contact convert path in Dynamics 365 Sales.

SalesTown CRM Contacts map to Dynamics 365 Sales Contact with full field-level preservation including name, phone, email, address, and any custom contact properties. We resolve the parent Account (from SalesTown Company) before Contact insert so that the AccountId lookup is satisfied. Owner assignment migrates by email match against the Dynamics 365 User table with a reconciliation queue for unresolved owners.

SalesTown CRM Company records map to Dynamics 365 Sales Account. The Company's domain or website field becomes the Account Website field and serves as a dedupe key during import. Account is the first record type loaded in production migration to satisfy the AccountId lookup required on Contact. The Company field schema in SalesTown is not publicly documented; we inspect the export and map available fields, flagging any unmapped columns for the customer's admin to review.

SalesTown CRM Deals map to Dynamics 365 Sales Opportunity. The deal amount, expected close date, owner, and stage migrate directly. We resolve the parent Account (via Company lookup), the Owner (via User email match), and the Record Type (via pipeline mapping) before Opportunity insert. Closed-Lost and Closed-Won statuses from SalesTown map to the equivalent Dynamics 365 stage values.

SalesTown CRM Pipelines map to Dynamics 365 Sales Record Types on the Opportunity object. Each Pipeline gets its own Record Type with a corresponding Sales Process that whitelists the stage values from the source pipeline. If SalesTown has multiple pipelines with different stage counts, each becomes a separate Record Type in Dynamics 365 Sales so that stage values remain scoped per line of business.

SalesTown CRM Stages map to Dynamics 365 Sales Stage values within the Sales Process. We map stage-to-stage explicitly rather than by position to handle source and destination pipelines with different stage counts. Stage probability percentages migrate from SalesTown to Dynamics 365 Sales StageProbability, rounded to the nearest allowed integer. Stage ordering within the Sales Process is preserved.

SalesTown CRM Activities (calls, emails, meetings) map to Dynamics 365 Sales Task and Event records. WhatsApp activities are the primary complexity: flat CSV exports split thread messages into individual rows, losing parent-child thread associations. We reconstruct thread relationships during the transform phase using timestamp ordering and sender IDs, rehydrating conversation continuity as grouped Task records with a custom WhatsApp thread reference field. Activity dates preserve the original SalesTown timestamps for timeline accuracy.

SalesTown CRM Users and Owners map to Dynamics 365 Sales User records via email address match. The migration user must have an active Dynamics 365 User record before any record import begins because OwnerId is a required reference on most standard objects. We extract every distinct Owner referenced on Leads, Contacts, Deals, and Activities, run email matching against the destination User table, and hold unresolved owners in a reconciliation queue for the customer's admin to provision before record load resumes.

SalesTown CRM custom email and communication templates have no documented schema for export. We attempt to extract available template metadata and body content from the export and flag template mapping as a post-migration cleanup task. Dynamics 365 Sales email templates are rebuilt by the customer's admin in the native template editor or migrated separately with the template body preserved as a text asset.