Migrate from ZeyOS to Pipedrive

ZeyOS Account records map directly to Pipedrive Organization. The Account name, address fields, phone, and website migrate as standard Organization fields. Account is imported before any Contact import so that the Organization relationship is resolved at the moment of Person insert. We use the Organization name as the dedupe key to avoid duplicate Organizations during import.

ZeyOS Contact records map to Pipedrive Person with name, email, phone, and address preserved. The parent Account reference resolves to a Pipedrive Organization by Organization name lookup. Any extdata fields (nickname, custom address fields) migrate as Person custom fields. Active status is preserved in a custom field so that inactive ZeyOS Contacts are flagged for manual review after import.

ZeyOS Lead is a distinct object separate from Contact. Pipedrive has no separate Lead object, so all Leads map to Person records with the original ZeyOS lead status preserved in a custom field lead_status__c. The customer chooses during scoping whether to create a separate Pipedrive pipeline stage or tag for migrated Leads to distinguish them from imported Contacts in reporting.

ZeyOS Items (inventory and product catalog) map to Pipedrive Products. The item name, SKU (barcode), model, and unit price migrate as Product fields. Stock quantity from ZeyOS's automated inventory transactions migrates as a Product custom field product_stock_qty__c. If the customer uses Pipedrive's Deals with Products feature, we create Pricebook entries during migration.

ZeyOS Projects are native Groupware objects with child Tasks and time entries. Pipedrive has no Projects object. We create a top-level Activity (type = Task with a specific subject pattern) for each Project and nest child Tasks as Activities linked by a custom parent_project_id__c field. Time entries from ZeyOS Projects migrate as separate Activity records with billable flag and duration preserved. The customer should decide during scoping whether Projects map this way or are treated as Deals with custom field groupings.

ZeyOS Tasks belong to Projects and have assignees, due dates, and status. They map to Pipedrive Activities (Tasks). The parent Project linkage is preserved via a custom field project_id__c. We map ZeyOS Task status to Pipedrive Activity status (open, completed). Due dates migrate with epoch-to-ISO conversion. Task priority maps to Pipedrive Activity priority.

ZeyOS Tickets are Helpdesk objects with email integration and subject-line ticket numbers. Pipedrive has no native Helpdesk or Case object, so Tickets map to Deals with a ticket_number__c custom field, status custom fields, and a dedicated pipeline (or pipeline stage) designated for support tickets. Email conversations attach to the Deal as Activity notes. For organizations that need separate case tracking, we recommend a dedicated Pipedrive add-on like Casely.

ZeyOS's four financial objects (Quote, Order, Delivery, Invoice) have no Pipedrive equivalents. We map them as Deals with a document_type__c custom field (values: Quote, Order, Delivery, Invoice), a document_status__c field, and the financial amount migrated as the Deal value. ZeyOS Invoices are audit-locked once booked: we flag these as read-only Deals with invoice_locked__c = true, set the status to Closed-Won at the time of the original ZeyOS invoice date, and sequence the import in strict chronological order. Any out-of-sequence locked invoices go to a manual review queue before import.

ZeyOS Contracts represent subscription or service agreements tied to Accounts. Pipedrive has no Contracts object, so we map contract metadata (contract ID, start date, end date, renewal terms, contract value) to Deal custom fields and link the Deal to the parent Organization. Contract-specific terms, renewal rules, and SLA terms are preserved in a contract_terms__c custom field as a text area.

ZeyOS Documents are stored as binary blobs in the files table's binfile column, linked by record FK. We download each binary blob via the ZeyOS REST API and re-upload to Pipedrive's file attachment storage linked to the mapped record (Organization, Person, or Deal). Files exceeding 25MB are flagged for customer manual review before import. Non-standard MIME types receive additional handling during staging.

ZeyOS exposes custom fields via the fields table and extdata JSON pattern in the REST API. We read every field definition, map the data type to the equivalent Pipedrive custom field type (text, number, date, dropdown, checkbox), and pre-create the Pipedrive custom field on the target object before the relevant records import. Multi-select picklists in ZeyOS map to Pipedrive multi-select fields. Custom field values from extdata are mapped during the transform step before insert.

ZeyOS Activities (calls, emails, notes) linked to Accounts or Contacts map to Pipedrive Activities. Call activities import with duration and disposition as Activity custom fields. Email activities import as Activity records with the email body preserved in the Activity subject or a custom field. All timestamps convert from Unix epoch to ISO 8601 during extraction.