Migrate from ZeyOS to Freshsales

ZeyOS Accounts are the primary company-level records linked to Contacts via a foreign key. We map them 1:1 to Freshsales Accounts, using the account name as the dedupe key. Account is created before any Contact import so that the parent-account lookup is satisfied at the moment of Contact insert. Any ZeyOS custom fields on Account (stored in extdata) map to Freshsales custom properties on the Account object.

ZeyOS Contacts store individual person records with name, email, and extdata fields. We map them 1:1 to Freshsales Contacts, resolving the parent AccountId from the ZeyOS foreign key before insert. Email address is the standard dedupe key. Any address fields, nickname, or custom contact properties stored in ZeyOS extdata map to Freshsales custom contact fields.

ZeyOS has a distinct Leads object separate from Contacts. Freshsales uses a unified Contact model with a Lead Status property rather than a separate Lead object. We merge ZeyOS Leads into Freshsales Contacts, preserving the ZeyOS lead status value in a custom Freshsales field (e.g., zeyos_lead_status__c) for reporting. If the customer's ZeyOS Leads have a meaningful qualification stage that predates their move to a Contact, we capture it as a contact property rather than discarding it.

ZeyOS Items represent the inventory and product catalog with barcode, model, and custom fields. We map them 1:1 to Freshsales Products, preserving product name, SKU (mapped to Freshsales product_code), and pricing information. Note that Freshsales Products are catalog entries without automated stock quantity tracking; ZeyOS's automated inventory transactions (triggered on deliveries) have no Freshsales equivalent. We flag any Items with non-zero stock quantities for customer review and document them as a custom reporting field or inventory-tracking workaround.

ZeyOS Tickets are the helpdesk object with email integration and subject-line ticket-number association. We map them to Freshsales Cases (available on the Growth and higher tiers) or to a custom Freshsales object if the destination is on the Free plan. Conversations, attachments, and custom ticket fields migrate to the corresponding Case fields and activity timeline. Ticket status from ZeyOS maps to a custom Case status field.

ZeyOS Users represent team members who own records, create files, and track time. We map them to Freshsales Users (sales reps and admins), resolving by email match. Any ZeyOS User without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive ZeyOS users are flagged for post-migration deactivation review.

ZeyOS Activities capture engagements (calls, emails, meetings, notes) linked to Accounts or Contacts. We map them to Freshsales Activities with the Who (Contact) and What (Account) references resolved from the migrated records. Timestamps stored as int8 Unix epoch in ZeyOS are converted to ISO 8601 datetime strings before insert into Freshsales. Activity type (call, email, meeting, note) maps to the corresponding Freshsales activity type.

ZeyOS files stored in the files table with binary blobs in the binfile column are exported via the REST API individually and re-uploaded as attachments to the corresponding Freshsales Contact, Account, or Case record. Files exceeding 25MB are flagged for customer review before import. The file name and MIME type are preserved; any non-standard MIME types receive manual handling.

ZeyOS exposes custom fields via the fields table and the extdata JSON pattern in the REST API. We read each field definition, identify its data type, and map it to the equivalent Freshsales custom property type (text, number, date, picklist, or checkbox). Custom field mapping is validated against Freshsales's property type constraints before import. Any ZeyOS custom fields without a Freshsales equivalent are flagged for customer review.