Migrate from Summit Service Systems to Microsoft Dynamics 365 Sales

Summit accounts map directly to Dynamics 365 Sales Account records. The Account.Name, Account.Website, and address fields translate one-to-one. Parent-account hierarchies in Summit map to Account.ParentAccountId in Dynamics 365; circular references are flagged before migration commits. All primary address components (street, city, state, postal code, country) transfer as standard address columns. If Summit stores multiple address lines, they concatenate into the primary address fields in Dynamics 365.

Summit contacts map to Dynamics 365 Sales Contact records. Standard fields (name, email, phone, title, address) map directly. Contacts without a parent account land in a default placeholder account until manually reassigned in Dynamics 365 post-migration. If a contact has multiple associated accounts, the most recently modified relationship becomes the primary account. Duplicate email addresses are flagged for review.

Summit leads migrate as Dynamics 365 Sales Lead records. Lead qualification status maps to the Lead.StatusCode picklist. Source attribution fields (LeadSource) transfer as custom or standard fields depending on Summit's field naming. Unqualified leads that should be contacts get flagged for manual review.

Summit opportunities map to Dynamics 365 Sales Opportunity records. Pipeline stages map to Opportunity.StageCode (or process stage names). Estimated close date and revenue fields transfer directly; probability percentages are reapplied based on Dynamics 365 stage mapping configuration. If Summit stores multiple pipelines, each pipeline requires a separate business process flow in Dynamics 365. Custom stage-specific fields, such as discount levels or competitor notes, become custom columns on the Opportunity table.

Summit's activity records split into Dynamics 365's activity types: phone calls become PhoneCall entities, emails become Email entities, meetings become Appointment entities. Original timestamps, subject lines, and owner assignments preserve. Regarding links attach activities to parent Account, Contact, or Opportunity records.

Summit notes and file attachments migrate to Dynamics 365 Sales Annotation entities. Rich-text formatting in notes is preserved where Summit's format is compatible; otherwise notes flatten to plain text. File attachments re-upload to SharePoint or Dynamics 365 native file storage depending on configuration.

Summit custom objects require new custom tables in Dynamics 365 Sales Dataverse. The table schema (column names, data types, relationships) is recreated. Custom objects that reference standard objects (Account, Contact) get Dataverse lookup columns pointing to those primary keys. Each custom table inherits the environment's security roles and uses the new_ prefix (or a custom prefix configured in your environment). Relationships between custom tables follow Summit's original cardinality.

Summit approval workflows and conditional routing have no direct Dynamics 365 Sales equivalent. These must be rebuilt in Power Automate or as Dynamics 365 workflow definitions. We export Summit's approval definitions as rebuild-reference documentation for your Dynamics admin. The exported reference captures multi-tier sign‑off steps, escalation rules, and field‑level conditions, guiding the design of corresponding cloud flows and mirroring security role restrictions.

Summit users map to Dynamics 365 Sales SystemUser records by email address matching. Unmatched owners are flagged before migration; your team either creates corresponding Dynamics users first or assigns records to a fallback owner. Active/inactive status in Summit transfers to User.Disabled in Dynamics 365.

Summit pipeline stages map to Dynamics 365 Sales business process stages. Each Summit stage name requires a value-mapping entry to the corresponding Dynamics StageCode picklist value. Stage order and probability percentages are reapplied based on Dynamics 365's process flow configuration.

Summit territory or region assignments map to Dynamics 365 Sales Territory records. If territories do not exist in Dynamics 365, they are created during migration. Territory-based routing rules must be reconfigured post-migration in Dynamics territory management settings. If Summit stores hierarchical territories, the hierarchy is recreated using Dynamics 365's parent‑territory lookup. Active status for each territory is transferred; inactive territories are archived as read‑only records.

Summit products map to Dynamics 365 Sales Product records. Unit of measure, pricing, and product hierarchy fields transfer. Bundle and discount configurations require manual review post-migration to ensure Dynamics price list structures match Summit's pricing model. If Summit tracks product images or descriptive attributes, those are stored in document library. Product relationships to accounts or opportunities are recreated via Opportunity Product and Quote Detail entities in Dynamics 365.

Summit quotes and orders migrate to Dynamics 365 Sales Quote, Order, and Invoice entities respectively. Status fields map to Dynamics statecode/statuscode conventions. Line items attach to parent Quote/Order records via QuoteDetail and SalesOrderDetail entities. Each line item retains its unit price, quantity, discount, and tax components. Custom pricing formulas are converted to Dynamics price list entries, and any attached notes or files move to the corresponding Quote or Order annotations.