Migrate from ZeyOS to Salesforce Sales Cloud

ZeyOS Accounts map directly to Salesforce Account as the primary company-level record. The account name, address fields, phone, and website transfer to the corresponding Account fields. Account is the parent of all Contact records in the destination, so we create Account before any Contact import to satisfy the AccountId Lookup foreign key at insert time. We use the Account name as the dedupe key during import.

ZeyOS Contacts map to Salesforce Contact with the parent AccountId resolved at migration time via email-domain or name matching against the migrated Accounts. The extdata fields (nickname, additional address fields) transfer to custom Contact fields created during schema design. Any ZeyOS Contact without a matching Account is held in a reconciliation queue for the customer to resolve before import resumes.

ZeyOS Leads map directly to Salesforce Lead. Lead status, source, and rating migrate to the corresponding Salesforce Lead fields. Any custom lead-scoring or lead-source fields stored in ZeyOS extdata transfer to custom Lead fields. We flag any ZeyOS Lead with no email address for customer review because Salesforce requires an email format for standard Lead creation.

ZeyOS Items (product catalog with barcode, model, and custom fields) map to Salesforce Product2. The Item name becomes Product Name, the item code becomes Product Code, and a Standard Price Book entry is created during import. Inventory quantities from ZeyOS's automated stock transactions do not map to a native Salesforce field and require a custom field or a separate inventory management AppExchange package post-migration.

ZeyOS Projects have no native Salesforce equivalent — Salesforce Sales Cloud has no standard Project object. We create a custom Project__c object during schema design with fields for name, description, status, start date, and end date. Child ZeyOS Tasks and time entries reference the migrated Project__c ID as their WhatId. The customer may alternatively assign Projects to a third-party project management AppExchange package installed post-migration.

ZeyOS Tasks belonging to Projects map to Salesforce Task with the WhatId resolved to the migrated Project__c ID. Assignee, due date, priority, and status transfer directly. Tasks without a parent Project map with WhatId set to the related Account or Contact. The original ZeyOS creationdate Unix timestamp is converted to ActivityDate on the Salesforce Task.

ZeyOS Tickets (helpdesk module with email integration and subject-line ticket numbering) map to Salesforce Case if the destination org includes Service Cloud. Ticket subject, description, status, priority, and origin migrate to the corresponding Case fields. Email thread history migrates as EmailMessage records linked to the Case via ParentId. Ticket custom fields from extdata transfer to custom Case fields.

ZeyOS Activities (calls, emails, meetings, and notes) split by type across Salesforce Task, Event, and EmailMessage. Calls map to Task with TaskSubtype = Call and call duration preserved. Emails map to Salesforce EmailMessage records linked to a parent Task record on the activity timeline. Meetings map to Event with StartDateTime, EndDateTime, and Location preserved. All activities resolve WhoId to the migrated Contact or Lead and WhatId to the related Account or Opportunity.

ZeyOS Users map to Salesforce User records by email match. We extract all distinct ZeyOS owner IDs referenced on Contacts, Accounts, Projects, and Tickets and match them against the destination org's User table by email. Users without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import continues, because OwnerId is required on most standard object inserts.

ZeyOS Quotes map to Salesforce Quote when the destination org includes Sales Cloud with the Quote object enabled. Quote status, expiration date, and line items map to the QuoteLineItems table with the Pricebook2 reference resolved at migration time. Quote PDFs are not stored as binary attachments in ZeyOS and do not migrate; the customer retains quote records as data-only.

ZeyOS Orders map to Salesforce Order linked to the parent Account. Order status, order date, and total amount transfer directly. Order line items map to OrderProduct records. We resolve the Pricebook2 reference before inserting line items. Note that ZeyOS marks orders as locked once the linked delivery is posted; we check the order status and flag any booked order for chronological review before import.

ZeyOS Deliveries (automated stock transactions linked to orders) have no direct Salesforce standard object equivalent. We create a custom Delivery__c object with fields for delivery date, status, linked order reference, and stock impact. Stock quantity changes from ZeyOS's automated inventory transactions do not map to Salesforce native fields and require a custom field or a separate inventory management AppExchange package post-migration.

ZeyOS Invoices are audit-proof — once booked, they cannot be edited or deleted via the ZeyOS API. We create a custom Invoice__c object to preserve the read-only state. The invoice date, amount, status, and line items migrate as custom fields. We sequence invoice imports in strict chronological order by invoice date and flag any out-of-sequence records for manual review before insertion to avoid locked-record conflicts. The customer confirms invoice chronology during scoping before migration begins.

ZeyOS Time Entries (billable or non-billable hours linked to Projects, Tasks, or Tickets) map to a custom TimeEntry__c object with fields for hours, date, description, billable flag, and a lookup to the parent Project__c or Case. OwnerId resolves to the migrated Salesforce User. ZeyOS's creationdate Unix epoch timestamp converts to the EntryDate custom field.

ZeyOS Contracts (subscription or service agreements tied to Accounts) map to Salesforce Contract with the AccountId resolved to the migrated Account. Contract start date, end date, and status transfer directly. Renewal terms and contract-specific custom clauses from extdata transfer to custom Contract fields. We flag contracts with missing Account references for customer review before import.

ZeyOS Documents are binary blobs stored in the binfile column of the files table, retrieved individually via the ZeyOS REST API. We download each file, determine its MIME type, and re-upload as a Salesforce ContentVersion record linked via ContentDocumentLink to the parent record (Account, Contact, Opportunity, Case, or Project__c). Files exceeding 25MB are flagged for customer review before import because Salesforce has a 25MB ContentVersion limit per file.

ZeyOS custom fields exposed via the fields table and extdata JSON pattern migrate to Salesforce custom fields on the corresponding object. We read the ZeyOS field definitions during discovery, create matching Salesforce custom fields (with __c suffix) of the appropriate data type during schema design, and then import extdata values as Salesforce field values. Picklist-style extdata values map to Salesforce picklist or multi-select picklist fields.

ZeyOS iXML scripting logic (custom process automation written in ZeyOS's proprietary scripting language) does not migrate. We deliver a written inventory of every active iXML script during scoping, documenting its trigger, conditions, actions, and the recommended Salesforce Flow equivalent. The customer's admin or a Salesforce implementation partner rebuilds the automation logic post-migration. This is outside standard migration scope.