Migrate from EZ Office to Freshsales

Pre-migration Freshsales schema setup

Before any data moves, your Freshsales admin (or our team) creates the custom fields, pick-lists, and custom objects needed for the migration. We deliver a schema setup plan based on your EZ Office custom field inventory, asset type count, vendor count, and location hierarchy depth so the Freshsales side is ready before validation runs. This includes creating the Vendor_Type__c pick-list, Location_Type__c pick-list, asset-tag and serial-number custom fields on Products, and the custom datetime fields for original create dates.

Resolve users and assign ownership

EZ Office system users (technicians, admins, managers) are matched to Freshsales users by email address. Unmatched users are flagged before migration; your team either invites them to Freshsales first or assigns their records to a fallback owner. No record lands in Freshsales without an OwnerId. For technicians who will own asset‑event Tasks, we verify that a matching Freshsales User exists with the appropriate profile. If no match is found, the record is placed in a holding queue and your admin receives a notification to either invite the user or assign a fallback owner.

Sequence migration: Vendors and Locations first, then Members, then Items and Assets

Freshsales requires Account records to exist before Contacts can associate to them. We sequence the migration to resolve foreign keys correctly: Vendors → Accounts, then Locations → Accounts with location-type tagging, then Members → Contacts linked to primary Account, then Items → Products with stock and barcode data, and finally Asset records linked to Products. Purchase Orders migrate last as Deals with vendor Account lookups.

Run a sample migration with field-level diff

A representative slice migrates first — typically 200–500 records spanning Items, Assets, Vendors, Locations, and Members. We generate a field-level diff between the EZ Office export and the Freshsales result so you can verify barcode field mapping, location hierarchy preservation, vendor-type tagging, and owner resolution before the full run commits. You approve the sample before we proceed to full load.

Full migration with delta-pickup and audit log

Full migration runs against Freshsales REST API with batch sizing and retry logic tuned to Freshsales rate limits. A delta-pickup window (24–48 hours) captures any records created or modified in EZ Office during the cutover so Freshsales reflects your final EZ Office state at go-live. All operations are logged in an audit trail, and one-click rollback is available if reconciliation identifies data discrepancies exceeding your tolerance threshold.

Post-migration verification and rebuild reference package

After migration, we run a reconciliation report comparing record counts, field-population rates, and file attachment counts between EZ Office and Freshsales. We deliver a rebuild reference document containing your EZ Office workflow definitions, report configurations, barcode-scanning logic, and approval chain setups so your Freshsales admin can reconstruct these in Freshsales Workflows, Report Builder, and Freshworks Marketplace apps. We do not migrate these — they require Freshsales-native redesign.