Migrate from EZ Office to Twenty CRM

EZO Members are the people who check out, use, and maintain assets. Each Member maps directly to a Twenty People record. Email, phone, and job-title fields translate 1:1. The Member's ID from EZO is stored as Source_System_ID__c on the Twenty People record for traceability. Members without email addresses are imported with a placeholder identifier and flagged for manual review.

EZO allows a Member to be assigned multiple assets simultaneously. Twenty People records support a primary Company link via companyId but don't natively support multi-asset assignment lists. We create a custom 'AssetAssignment' junction object in Twenty linking People to the imported Asset records, preserving which assets a Member currently holds and historically held.

EZO Vendors are organizations that supply equipment, parts, or services. They map directly to Twenty Companies records. The vendor's name, website, contact information, and address fields map to the corresponding Twenty Company fields. We tag each vendor record with a custom 'Company_Type__c' field set to 'Vendor' so teams can filter vendor companies separately from customer accounts.

EZO Locations represent physical sites, rooms, or storage areas where assets are stored or deployed. In Twenty, which lacks a native Location object, we map Locations to Company records with a custom 'Location__c' boolean flag. The full hierarchical path (e.g., Building A → Floor 2 → Room 204) is preserved in a custom text field if EZO's 'Show hierarchical location in item listings' setting was enabled.

EZO Assets are the core data entity—serialized equipment, fleet items, or tracked inventory with lifecycle states (Available, Checked Out, In Maintenance, Retired). Twenty has no native Asset object. We create a custom 'Asset__c' object in Twenty with fields for name, serial number, asset tag, status, and purchase date. Each Asset links to a Company (the owning organization or the member who checked it out) via a relation field.

EZO inventory tracks stock quantities of consumable or serialized items. When inventory represents items for sale or service deals, we create Opportunity records in Twenty with the item name, quantity, and expected close date. For purely operational stock tracking (spare parts, supplies), we create a custom 'Inventory__c' object with quantity_on_hand and reorder_point fields. The split is determined by the inventory category set in EZO.

EZO records check-in/check-out events, custody transfers, and maintenance activities with timestamps and assigned user. Each event maps to a Twenty Task record linked to the relevant Asset__c and People records. The task subject captures the event type (e.g., 'Checked Out to John Smith'), and the task due date captures the event timestamp. This preserves the full operational audit trail on the asset record.

EZO documents attached to assets, vendors, or locations export via the 'export documents data' function. In Twenty, documents attach to the corresponding record (Asset__c, Company, or People) as Notes with a link to the file URL. If EZO documents are stored in Dropbox (a supported integration), we re-upload them to Twenty's file storage or a linked cloud location.

EZO custom fields on Assets, Members, Vendors, and Locations are extracted during the CSV export. In Twenty, each custom field must be pre-created in Settings → Data Model with the matching field type (text, number, select, date, etc.). We deliver a custom field creation plan before migration runs so the Twenty schema is ready to receive the imported data without type-mismatch errors.

EZO Reports are pre-built or custom report definitions with filtering and grouping logic. Twenty has no equivalent report builder that preserves EZO's report structure. The underlying data (Assets, Vendors, Members) migrates, but EZO report definitions must be rebuilt in Twenty's views and filtering system. We provide a report-rebuild reference document mapping each EZO report to the corresponding Twenty view configuration.