Migrate from SortScape to Microsoft Dynamics 365 Sales

SortScape Client records map 1:1 to Dynamics 365 Accounts. The client's business name becomes Account.Name; client phone and email become telephone1 and emailaddress1 on the account. If the client is an individual homeowner rather than a business, the record maps to Contact with the Account as a household or individual account type.

SortScape stores a primary contact name and phone on each client record. These map to Contact.FirstName, Contact.LastName, Contact.Phone, and Contact.Email. When SortScape has multiple contacts per client, each becomes a separate Dynamics 365 Contact linked to the same Account via the AccountId lookup.

SortScape properties represent physical sites (addresses, block/lot numbers, access notes). Each property is stored as a separate SortScape record with a link to the client. In Dynamics 365, the property address becomes a second Account record of type 'Property Site' or is stored as a custom field block on the primary Account. Access notes and special instructions migrate as custom text fields on the Account.

SortScape visit records represent scheduled jobs at a property. FlitStack maps each completed visit to a Dynamics 365 Opportunity with the client Account as the parent, the visit date as CloseDate, and the service fee as Amount. Open visits become Opportunities with a status of 'Open' and a pipeline column matching the SortScape service type.

SortScape visit statuses (Scheduled, In Progress, Completed, Cancelled) map to Dynamics 365 Opportunity Stage values. 'Completed' maps to 'Closed Won', 'Cancelled' maps to 'Closed Lost', and open statuses map to the appropriate stage in the configured Sales Process. The mapping is configurable per the client's current pipeline stages.

SortScape service types (e.g., Lawn Mowing, Garden Maintenance, Tree Trimming) are mapped to a custom Opportunity field called Service_Type__c so that Dynamics 365 reports can filter pipeline by service category. If no custom field is desired, the service type is stored in the Opportunity Description field.

SortScape records the client creation date. Dynamics 365's CreatedDate is set at migration time, which breaks historical reporting continuity. FlitStack preserves the original SortScape create date as a custom datetime field on Account so that age-of-client reports remain accurate post-migration.

SortScape team members are the people who perform visits. These map to Dynamics 365 Users if they are CRM users, or to Contacts if they are subcontractors or external staff. FlitStack resolves each SortScape team member by email against the destination Dynamics 365 user list — unmatched team members are flagged for manual assignment before the full migration runs.

SortScape property photos and site images are downloaded from the SortScape export and re-uploaded to the corresponding Dynamics 365 Account's SharePoint document location. If SharePoint is not configured, notes with base64-encoded image references are created on the Account record. This preserves the visual record but is not a native Dynamics 365 photo field.

SortScape integrations with Xero mean some clients have linked invoice IDs in SortScape. FlitStack migrates these as a custom text field Xero_Invoice_Ref__c on the Opportunity for reconciliation continuity. The Xero connection itself must be rebuilt in Dynamics 365 via the Xero connector or Power Automate.

SortScape's route-optimization output — optimized visit order, crew assignments, and travel-time estimates — has no equivalent in Dynamics 365 Sales. FlitStack exports this data as a standalone CSV reference file. Rebuild options include Power Automate with a mapping connector or a third-party routing add-in from AppSource.

SortScape custom fields on Client and Property records are identified during the pre-migration audit. Each custom field is created in Dynamics 365 with the appropriate Dataverse data type before data loading begins. Pick-list fields in SortScape are recreated as Option Sets in Dynamics 365 with the same value labels.