Migrate from EZ Office to Microsoft Dynamics 365 Sales

EZ Office assets have no direct CRM equivalent in Dynamics 365 Sales. We create an Asset__c custom table linked to Account via a lookup field. Original asset ID stored as Source_Asset_ID__c for traceability and delta-run de-duplication. This mapping preserves all asset metadata, warranty information, and custody records in the new CRM structure.

EZ Office vendors map to Dynamics 365 Sales accounts. Vendor type field in EZ Office maps to Account Type (Vendor). Vendor address, contact name, and payment terms migrate as Account fields. Vendors without a primary contact land as accounts with a default notes section.

EZ Office hierarchical locations (site/building/floor/room) require a custom Location__c table with self-referencing Parent_Location__c lookup for hierarchy. Dynamics 365 Sales has no native multi-level location entity, so we build the structure as a custom table linked to Account for site-specific asset assignment.

EZ Office inventory items with stock quantities, reorder points, and unit costs map to a custom Inventory_Item__c table linked to Asset__c. Quantity on hand, reorder level, and last-count date migrate as custom number fields. Inventory valuation logic requires manual rebuild in Dynamics 365 Finance or a separate inventory module.

EZ Office members (people assigned assets or managing inventory) map to Dynamics 365 Sales contacts. Email, name, phone, and department fields migrate directly. Member status (active/inactive) maps to a custom Contact Status field. EZ Office admin users who are not Dynamics 365 licensed users get a Contact record with Source_User_ID__c.

EZ Office custody history — who checked out an asset and when — translates to a series of Task records attached to the Asset__c custom table. Each transfer becomes a completed Task with Subject = 'Custody Transfer', Description = 'Transferred from [Previous Holder] to [New Holder]', and Actual Duration capturing the custody period. Original timestamps and handler names are preserved.

EZ Office maintenance logs map to Task records on Asset__c with Type = 'Maintenance'. Service date, vendor (linked Account), cost, and resolution notes migrate as Task fields. Recurring maintenance schedules are surfaced as rebuild references for Power Automate — the recurrence pattern itself cannot migrate automatically.

EZ Office purchase orders map to a custom Purchase_Order__c table linked to the vendor Account and the Asset__c or Inventory_Item__c it relates to. PO number, date, status, total amount, and line items migrate as fields. Dynamics 365 Sales does not have native purchase order management — this requires a rebuild in Dynamics 365 Finance or a third-party procurement app.

EZ Office documents attached to assets, vendors, or inventory items re-upload to SharePoint document libraries associated with the corresponding Account or Asset__c record. File size limits apply. Inline images or PDFs stored in EZ Office download and re-upload to the linked SharePoint library with original filenames preserved.

EZ Office canned reports (asset depreciation, inventory valuation, vendor activity) have no direct Dynamics 365 Sales equivalent. We export report definitions and field selections as a rebuild reference for Power BI or Dynamics 365 custom reports. The underlying data migrates; the report layouts do not.

EZ Office custom fields on assets (e.g., insurance policy number, lease expiry, equipment model) migrate as custom fields on the Asset__c table. Field type mapping: text → Text, number → Number, date → Date, dropdown → Picklist. Field-level security settings applied per Dynamics 365 field customization rules.

EZ Office groups (departments or teams managing assets) map to Dynamics 365 Sales Teams. Group permissions and access rules require manual rebuild in Dynamics 365 Security Roles and Team structure. Group membership lists are preserved as a reference for your admin to reassign during the setup phase.