Migrate from Uptick to Microsoft Dynamics 365 Sales

Uptick customers map directly to Dynamics 365 Sales accounts. Customer name, address, and contact information translate as Account.Name and the address composite fields. Primary email maps to Account.Email or a custom field if the primary contact is the account-level contact.

Uptick locations represent physical sites (warehouses, office buildings) linked to customers. If each location maps to a separate billing or service account, we create child accounts under the parent customer. If locations are informational, we create a custom Location__c table linked to the parent Account.

Uptick assets (fire extinguishers, suppression panels) map to Dynamics 365 Field Service Assets table or a custom Asset__c table in Dataverse. Asset type, serial number, install date, and next service due date map to corresponding columns. Parent-child asset relationships require recursive mapping logic.

Uptick work orders map to Dynamics 365 Cases for reactive service or to Field Service Work Orders if the Field Service module is licensed. Work order status, priority, scheduled date, and completion notes map to Case.Title, Priority, CreatedOn, and Description. Line items (parts used) map to Case Products or a custom WorkOrderLine__c table.

Uptick quotes (with line items for products and labor) map to Dynamics 365 Opportunities with OpportunityLineItems. Quote total maps to Opportunity.Amount. Quote status (draft, sent, accepted) translates to Opportunity.StageName values. Products and services map to OpportunityLineItem.ProductId and Quantity, preserving unit price, quantity, and product description. If Uptick quotes include discount percentages, these map to OpportunityLineItem.DiscountPercent or DiscountAmount fields so your sales team sees the full pricing breakdown in Dynamics 365.

Uptick contacts map directly to Dynamics 365 Sales Contacts. First name, last name, email, phone, and job title translate 1:1. Multiple contacts per customer map to multiple Contact records linked to the same AccountId. During migration, we match contacts by email first—if a Contact already exists in Dynamics 365, we link to it rather than creating duplicates. Any Uptick contact without a matching email creates a new Contact record.

Uptick technicians and admin users map to Dynamics 365 Users by email match. For Field Service dispatch, technicians also map to Bookable Resources linked to User records. Unmatched users are flagged before migration for your admin to create or invite. During the sample migration, we generate a user resolution report showing which Uptick emails resolved to existing Dynamics 365 Users and which require new user creation, preventing orphaned work order records.

Uptick products (materials) and services (labor rates) map to Dynamics 365 Product records. Product type distinguishes between inventory items (ProductTypeCode=1) and services (ProductTypeCode=2). Supplier information maps to a custom field if not in the standard Product schema. During migration, we validate that Uptick product codes exist as active Products before importing quotes—if a product is missing, we flag it for your admin to create.

Uptick inspection records with pass/fail results and photos map to Dynamics 365 Notes (for text summaries) or a custom Inspection__c table linked to the parent Asset. Photos are downloaded and re-uploaded as Salesforce Files or SharePoint attachments. Inspection dates map to custom datetime fields for compliance reporting.

Uptick certification records (inspection certificates, compliance documents) have no direct Dynamics 365 equivalent. We create a custom Certificate__c table in Dataverse linked to the parent Asset, with fields for certificate number, issuing body, expiry date, and document attachment. Expiry alerts require Power Automate flows post-migration.

Uptick custom fields per asset type (fire code compliance fields, regulatory codes) map to custom columns on the Dynamics 365 Asset table. Column naming follows Dataverse conventions (new_ prefix). We create all custom fields before migration so field mapping applies correctly.

Uptick file attachments on work orders and assets are downloaded and re-uploaded to Dynamics 365 SharePoint integration or as Notes attachments. Original file names and create dates are preserved. File size limits apply per Dynamics 365 (default 128MB per file).