Migrate from EZ Office to Salesforce Sales Cloud

EZOfficeInventory Vendors map directly to Salesforce Accounts with Account.type='Vendor'. Vendor contact records within EZO migrate as Account Contacts in Salesforce. Primary vendor address maps to BillingAddress on the Account record. If your vendor list includes parent‑company relationships, we also map them to Account hierarchies using the ParentAccountId field to preserve corporate structures.

EZOfficeInventory Assets map 1:1 to Salesforce Asset records. Asset.SerialNumber, Asset.Name, InstallDate, Status, and UsageEndDate carry over. The Salesforce Asset.AccountId lookup resolves to the Account migrated from the vendor or a customer Account. For assets that are currently checked out, we also map the latest assignment to the AssetContactRelation junction object, preserving current custody information.

EZOfficeInventory items with stock quantities and pricing map to Product2 with the 'Quantity Book' feature enabled. Stock-on-hand quantity migrates to a custom field (Inventory_Quantity__c) since Product2 does not natively track real-time stock. If your items have lot or serial numbers, we can also create a custom Lot_Serial__c field on Product2 to keep track of those identifiers in Salesforce.

Non-inventory items (consumables, services) map directly to Product2 as standard products without inventory tracking enabled. These items can still include pricing, description, and product code fields. If they are tied to a vendor, we link them to the vendor Account via a custom Vendor_Account__c lookup to maintain procurement context.

EZOfficeInventory's hierarchical locations (Site > Building > Room) require a custom Location__c object in Salesforce with parent-location lookup (Location__c.Parent_Location__c) to preserve the full hierarchy. Account. BillingAddress captures the lowest-level location for address display. We also generate a mapping CSV that lists each location’s Salesforce ID and its parent ID, so the hierarchy can be bulk‑loaded using Data Loader or REST API.

EZOfficeInventory Members are internal staff who check out assets. They map to Salesforce Contacts on a designated 'Internal' Account or to Salesforce Users if they also log into Salesforce. Email match resolves to existing Users. If a Member’s email does not match an existing User, we create a new Contact record and flag it for your admin to provision Salesforce access as needed.

EZOfficeInventory's check-out/assignment history maps to Salesforce AssetContactRelation or a custom Assignment_History__c junction object linking Asset to Contact, preserving assignment date and return date. We include both the check‑out and check‑in timestamps as separate datetime fields, and we also capture the member’s department and location at the time of checkout for audit purposes.

Documents attached to Assets or Inventory items in EZOfficeInventory re-upload to Salesforce Files (ContentDocument/ContentVersion model). File size limits apply; inline images in notes downloaded and rehosted. We also map file metadata such as created date, last modified date, and owner to the corresponding ContentVersion record, preserving the original author information in Salesforce.

EZOfficeInventory custom fields on Assets migrate to custom fields on Salesforce Asset with the __c suffix. Field data type is preserved where possible; complex EZO field types may require Salesforce formula fields or pick-lists. If a custom field uses a multi-select list in EZO, we convert it to a Salesforce multi-select picklist on the __c field, maintaining all selected values.

EZOfficeInventory canned reports and custom reports do not migrate. Data underlying reports migrates fully. We deliver a report-migration reference document mapping EZO report columns to Salesforce Report builder equivalents. The reference includes the original report’s filters, groupings, and chart types, along with suggested Salesforce Report Builder configurations to replicate the same insights.

EZOfficeInventory Groups (departments, cost centers) map to a custom Group__c object in Salesforce, linked to Assets via a lookup field. This preserves grouping context without Salesforce-native equivalent. If your groups have hierarchical relationships, we can also add a Parent_Group__c lookup to the Group__c object, mirroring the department structure in Salesforce.

Vendor contacts within EZOfficeInventory migrate as AccountContactRole records on the mapped Vendor Account, with role type preserved ('Primary Contact', 'Billing Contact', etc.). If a vendor contact also needs to be a Salesforce User, we can convert the AccountContactRole to a Contact record and link it to a User profile, ensuring they can log in to Salesforce.