Migrate from Pure Chart to Microsoft Dynamics 365 Sales

Pure Chart contacts migrate directly to Dynamics 365 Contact records. The EmailAddress1 field maps to the primary email, and Phone field maps to Telephone1. OwnerId is resolved by email match against Dynamics 365 SystemUser records — unmatched contacts are flagged before the migration commits to a fallback owner.

Pure Chart contacts that have not progressed to a sales-qualified stage split into Dynamics 365 Lead records. Leads that already have a deal association or a closed-won status route to Contact instead. The source contact stage or status field determines the split rule — FlitStack surfaces this mapping in the pre-migration field-level diff.

Pure Chart company records map 1:1 to Dynamics 365 Account. Account.Name maps directly, and the Website field populates WebSiteURL. If Pure Chart stores a parent-company relationship, the ParentAccountId lookup is resolved against already-migrated Account records — circular references are flagged before the load.

Pure Chart deal records map to Dynamics 365 Opportunity. The Opportunity Name maps from dealname, Amount from deal_value or amount, and CloseDate from closedate. The pipeline and stage in Pure Chart map to a Sales Process and StageName value — each unique pipeline in Pure Chart generates a corresponding Dynamics 365 Sales Process.

Pure Chart pipelines do not have a direct Dynamics 365 equivalent. Each unique pipeline becomes a Sales Process in Dynamics 365 Sales. Stage names within the pipeline are mapped to the StageName pick-list values on the Opportunity record for that process. Probability and forecast category are applied per stage from a mapping table supplied during planning.

Stage names in Pure Chart map value-by-value to Dynamics 365 StageName pick-list entries on the corresponding Sales Process. Each stage mapping includes probability weight and forecast category assignment — these are set during migration and can be adjusted by the Dynamics 365 admin post-migration.

Pure Chart call logs migrate to Dynamics 365 PhoneCall activity records. The Subject field captures the call title, and Description holds the outcome or notes. Call duration, direction (inbound/outbound), and the parent Contact or Opportunity lookup are preserved from the source activity record.

Pure Chart email logs migrate to Dynamics 365 Email activity records. The subject, body, from/to addresses, and timestamp are mapped. Email attachments are extracted and re-hosted in SharePoint or Dynamics 365 native file storage, with the file link preserved on the Email record.

Pure Chart meeting records migrate to Dynamics 365 Appointment. Start time, end time, location, subject, and body are preserved. The regarding lookup links the appointment to the source Contact, Account, or Opportunity. Recurring meeting series are stored as a separate recurrence pattern on the Appointment record.

Pure Chart notes migrate to Dynamics 365 Annotation records. The NoteText field maps to Annotation.NoteText. Rich-text formatting is preserved where Pure Chart supports it. The object lookup (regarding_objectid) is set to the migrated parent record ID so the note appears in context on the Account, Contact, or Opportunity.

Pure Chart file attachments are extracted, downloaded, and re-uploaded to SharePoint or Dynamics 365 native file storage. A SharePoint Document Location record is created and linked to the regarding Account or Contact. Files exceeding Dynamics 365 default size limits are flagged for admin decision before the migration run.

Pure Chart custom objects that have no standard Dynamics 365 equivalent are created as custom tables with the new_ prefix. The migration plan documents each custom object, its fields, and the target table schema. Custom table relationships that are many-to-many in Pure Chart are modeled as Dataverse many-to-many intersect tables or as lookup-based one-to-many relationships.

Pure Chart custom fields are mapped to new_* columns on the corresponding Dynamics 365 standard table. Field data type is mapped: text fields become nvarchar, number fields become integer or decimal, date fields become datetime. Pick-list values in Pure Chart migrate as option-set values on the custom column.

Pure Chart owner references are resolved by email address against Dynamics 365 SystemUser records. FlitStack generates a pre-migration owner resolution report: users present in Dynamics 365 are matched, and records for unmatched owners are assigned to a designated fallback user. Your Dynamics 365 admin can invite the missing users before the final migration run.