Migrate from Simple Sales Tracking to Microsoft Dynamics 365 Sales

Simple Sales Tracking Leads map directly to Dynamics 365 Lead. Lead source, status, and any custom Lead-level properties migrate as typed Dataverse attributes. We resolve the Dynamics 365 Lead Status picklist against the default Sales Process before import. Owner assignment maps by email match against the destination User table.

Simple Sales Tracking Opportunities map to Dynamics 365 Opportunity. Deal amount, expected close date, and owner migrate directly. The custom pipeline stage names from Simple Sales Tracking are mapped to Dynamics 365 Stage values within a Sales Process that we configure before migration. We preserve any Closed-Won or Closed-Lost disposition values in custom Opportunity fields.

Simple Sales Tracking Accounts map to Dynamics 365 Account. Account name, address fields, industry tag, and associated contact references migrate. Account is created before Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. We use Account Name as the primary dedupe key.

Simple Sales Tracking Contacts map to Dynamics 365 Contact. Name, email, phone, and address fields migrate directly. We resolve Contact-to-Account linking by matching the Simple Sales Tracking Account reference against the migrated Account Name or domain. Any Contact without a resolved AccountId is held in a reconciliation queue for the customer admin to address before production cutover.

Simple Sales Tracking custom fields on Sales Records require manual field definition discovery from the platform's UI metadata, since no schema endpoint exists. We ask the customer to provide a screen capture of their custom field configuration page during discovery. Each custom field is then pre-created in Dynamics 365 with the appropriate Dataverse type (string, integer, decimal, or picklist) before any data import begins. Fields that have no compatible Dynamics 365 type are exported as text with a migration note flagging the data loss.

Simple Sales Tracking's custom stage names and stage sequence are captured during discovery. We create a corresponding Microsoft Dynamics 365 Sales Process with Stage values that match the source names and ordering as closely as the destination picklist allows. Stages with no clear equivalent in Dynamics 365's default set are added as custom Stage values with a probability percentage mapped from the source.

Simple Sales Tracking Appointments map to Dynamics 365 Appointment. Start time, end time, duration, subject, and linked Contact reference migrate. The Contact lookup is resolved against the migrated Contact record using email as the matching key. Appointment location and description map to Location and Description fields respectively.

Simple Sales Tracking Tasks map to Dynamics 365 Task. Due date, subject, assignee (Owner), and completion status migrate. Open tasks land with Status = Open; completed tasks land with Status = Completed and an ActualDuration preserved in a custom field. Task assignment uses email-to-User matching against the destination org.

Simple Sales Tracking Notes migrate to Dynamics 365 Note (or Annotation) records linked via Regarding to the parent Contact, Account, or Opportunity. Note body and timestamp preserve. We do not guarantee retention of text formatting or embedded file links; any such content is flagged in the migration report.

Simple Sales Tracking file attachments (up to the 1 GB account limit) are downloaded individually and re-attached in Dynamics 365. Files linked to Accounts and Opportunities are stored in SharePoint Document Locations created during migration; files linked to Contacts are stored in the Contact's default SharePoint location. Files exceeding what can be reasonably migrated via API are listed in a file migration manifest for manual re-upload by the customer admin.

The Simple Sales Tracking Activity Feed is a real-time event stream generated within the application and is not exposed as a queryable data object via the API. There is no historical query endpoint for feed entries. We do not migrate the Activity Feed. We advise customers to export any critical feed entries as manual Notes in Simple Sales Tracking before the migration date so that the content can be captured as Note records in Dynamics 365.

Simple Sales Tracking multi-level user permissions are mapped to Dynamics 365 Security Roles. We export the permission structure from the source and produce a mapping table that maps each Simple Sales Tracking role to the closest applicable Dynamics 365 role (e.g., Salesperson, Sales Manager, System Administrator). The customer's Dynamics 365 admin applies the roles post-migration.