Migrate from ZeyOS to Microsoft Dynamics 365 Sales

ZeyOS Accounts map directly to Microsoft Microsoft Dynamics 365 Sales Account (the company-level record). We use the account name as the primary dedupe key during import and preserve any external ID from ZeyOS's extdata fields as a custom field on the Dynamics 365 Account for cross-system reference. Account is imported before Contact to satisfy the primary contact lookup relationship.

ZeyOS Contacts map to Microsoft Dynamics 365 Sales Contact. The parent Account reference resolves at import time by matching the ZeyOS account FK to the newly created Dynamics 365 Account record ID. We preserve ZeyOS nickname and address fields from extdata as custom Contact fields and convert any date fields from Unix epoch to Dataverse datetime format.

ZeyOS Leads are a distinct CRM object and map to Microsoft Dynamics 365 Sales Lead. Lead status and lead score values from ZeyOS custom fields migrate as custom Lead properties. Any ZeyOS lead-specific fields that have no direct Dynamics 365 equivalent become custom fields on the Lead entity.

ZeyOS Deals map to Microsoft Dynamics 365 Sales Opportunity. The ZeyOS dealstage property maps to Dynamics 365 StageName. Pipeline assignments from ZeyOS map to Opportunity Record Types or Sales Processes that we configure before migration. Closed-Lost and Closed-Won reasons migrate as custom Opportunity fields.

ZeyOS Items (inventory and product catalog) map to Microsoft Dynamics 365 Sales Product2 records. The ZeyOS barcode and model fields migrate as custom Product2 fields. Stock quantities from ZeyOS's automated inventory tracking require customer review for mapping to Dynamics 365 Inventory Management or a separate inventory module.

ZeyOS Tickets map to Microsoft Dynamics 365 Sales Case (Incident entity in Dataverse). Ticket pipeline stages become Case status values, and ticket conversations migrate as EmailMessage records linked to the Case. Subject line ticket-number associations are preserved as a custom Case field.

ZeyOS Projects map to Dynamics 365 Project Service entities. The project hierarchy (parent project with child Tasks and time entries) requires configuration in the destination environment to set up the correct project structure. Time entries from ZeyOS map to the BookableResourceBooking entity. Customer chooses whether Project Service licensing is required or if Tasks serve as the project tracking equivalent.

ZeyOS Tasks belong to Projects and map to Microsoft Dynamics 365 Sales Task. Parent-Project linkage preserves through the project configuration step. Task assignees resolve by matching ZeyOS owner email to the User record in the destination org.

ZeyOS files table stores binary blobs that we download individually from the REST API and re-upload to Dynamics 365 SharePoint integration or as Note attachments. Files exceeding 25MB are flagged for customer review. Document associations (record FK or comment FK) map to SharePoint document location or Note parent record references.

ZeyOS financial pipeline objects (Quotes, Orders, Deliveries, Invoices) merge into the Microsoft Dynamics 365 Sales Opportunity with financial field extensions. We preserve ZeyOS invoice chronology because invoices are audit-locked once booked; we sequence them in strict chronological order and flag any out-of-sequence invoices for manual review before import. Financial totals and line items become custom Opportunity fields or related OpportunityProduct records.

ZeyOS Contracts map to Microsoft Dynamics 365 Sales Contract with metadata preserved (contract number, start date, end date, account link). Renewal rules and contract-specific terms require manual review in the destination system post-migration because Dynamics 365 Contract renewal logic may differ from ZeyOS behavior.

ZeyOS Users map to Microsoft Dynamics 365 Sales User records. We match by email address. Inactive ZeyOS users are flagged for deactivation review in Dynamics 365. User provisioning in the destination org must complete before record migration begins because OwnerId references are required on most standard entities.