Migrate from EZ Office to Nutshell

Nutshell has no native asset-equivalent object. FlitStack AI creates a custom Asset object in Nutshell and maps all ez-office standard fields (name, barcode, serial number, status, purchase date, cost, assigned user) as custom fields on that object. The custom object is accessible in Nutshell's UI alongside People, Companies, and Leads.

When an ez-office Asset has an assigned User (custodian), the user record is resolved via email match into a Nutshell Person. The asset's custom object record then links back to that Person via a custom Person lookup field. Unmatched custodians are flagged so your team can decide whether to invite them as Nutshell users or assign the asset to a placeholder person.

ez-office tracks every custody hand-off as a discrete event with a timestamp, a from-user, a to-user, and a note. Nutshell has no native custody log. FlitStack AI creates a Task for each custody event with Subject set to 'Custody Transfer: [Asset Name]', Type set to 'Custody Transfer' (a custom Task type), the original event timestamp preserved, and a custom field linking back to the asset's custom object record.

ez-office Users who log into the platform to manage assets translate directly to Nutshell People. The migration maps email address, full name, phone number, role title, and department. Active/inactive status in ez-office is preserved as a custom Status__c field on the Nutshell Person since Nutshell People do not have a native active/inactive flag separate from user licensing.

ez-office Vendors are companies that supply or service tracked assets. FlitStack AI maps Vendor records to Nutshell Companies, sets a custom Vendor_Type__c field to 'Asset Vendor' to distinguish them from customer accounts, and preserves the vendor's contact name, phone, and email in the Nutshell Company record's primary contact fields. Vendor-specific fields (tax ID, payment terms) are preserved as custom text fields on the Company.

ez-office Inventory items (stock items, consumables, parts tracked separately from Assets) map directly to Nutshell Products. The Product Name, SKU, unit cost, quantity on hand, and vendor link (mapped to a related Company) are preserved. Stock-threshold alerts from ez-office are stored as custom fields on the Nutshell Product since Nutshell does not have a native reorder-alert mechanism.

ez-office Location records form a hierarchical tree (building > floor > room > shelf). Nutshell has no native Location object. FlitStack AI serializes the full location path into a custom text field (Location_Full_Path__c) on the Asset custom object. If your team uses specific sub-location fields (building, room), each is stored as a separate custom field on the Asset object for filtering in Nutshell.

ez-office Groups define asset categories (IT Equipment, Lab Instruments, Vehicles). FlitStack AI maps each unique Group name to a custom pick-list value on the Asset object's Category__c field. If a group tree exists (parent group > child group), the top-level group becomes the pick-list value and sub-group is stored in a secondary custom text field.

ez-office Asset Stock tracks countable quantities of identical items. FlitStack AI maps the stock item to a Nutshell Product with the quantity-on-hand value from ez-office. Each stock movement record in ez-office is translated to a Nutshell Activity Note attached to the Product, noting the movement type (received, issued, adjusted) and the resulting quantity change.

ez-office Documents attached to Assets (manuals, certificates, photos) are downloaded and re-uploaded as file attachments on the corresponding Nutshell Asset custom object record. Documents attached to Vendor records are attached to the mapped Nutshell Company. The original file name and upload date from ez-office are preserved in the Nutshell attachment metadata.

ez-office canned report definitions (column layouts, filter configurations) have no equivalent in Nutshell's reporting model. FlitStack does not migrate report definitions. The underlying data — asset lists, user lists, stock reports — migrates fully into Nutshell custom objects and Products so your team can build Nutshell-native reports on the migrated data after go-live.

ez-office maintenance work orders and scheduled service records are maintenance-management constructs with no direct equivalent in Nutshell's deal-and-activity model. FlitStack preserves the work order data as a CSV export alongside the migration for reference, but these records do not map to Nutshell objects and must be handled in your destination maintenance-management tool separately.