Migrate from ZeyOS to HubSpot

ZeyOS contact records map 1:1 to HubSpot contacts. ZeyOS stores company name inline on the contact — we extract it, create or match a HubSpot Company record first, then link the contact to it via the primary company Association. Email uniqueness is enforced in HubSpot; duplicates are surfaced before the full migration runs.

ZeyOS lead records map to HubSpot leads. ZeyOS lead status values (open, converted, lost) map to HubSpot lead status properties. ZeyOS records that have been converted to contacts in ZeyOS are handled separately — we route them to HubSpot contacts rather than leads to avoid duplicates.

ZeyOS company records map 1:1 to HubSpot company records. ZeyOS stores address, industry, employee count, and revenue inline. HubSpot company properties (industry, number of employees, annual revenue) receive these directly. ZeyOS company hierarchies (parent/child) map to HubSpot's parent company field.

ZeyOS deals map to HubSpot deals (internally named Opportunities). ZeyOS pipeline names become HubSpot deal pipeline names. ZeyOS deal stage values map to HubSpot deal stage values — value-by-value mapping is required because stage names differ between ZeyOS pipelines. Probability, forecast category, and stage order are preserved as HubSpot properties.

ZeyOS helpdesk tickets map directly to HubSpot support tickets. Subject, description, status, priority, type, and resolution time map to HubSpot ticket properties. ZeyOS ticket contact associations link to HubSpot ticket contacts via the contact's HubSpot ID. ZeyOS ticket-task associations are preserved as HubSpot ticket task associations.

ZeyOS invoices and quotes carry line-item detail with product, quantity, price, tax, and discount — no native HubSpot equivalent exists. We migrate these as a custom ZeyOS_Invoice__c object with line items stored as a JSON property or a related custom Line_Item__c object. The rebuild path uses HubSpot's Payments product and a document template for PDF quotes.

ZeyOS tasks map to HubSpot engagement tasks. Subject, due date, status, priority, and description transfer directly. ZeyOS task contacts are linked via HubSpot contact associations. ZeyOS task owner resolves against HubSpot users by email match — unmatched owners are flagged and assigned to a fallback owner before the full migration.

ZeyOS calendar events map to HubSpot meetings (engagement type 'meeting'). Title, start/end timestamps, body, and attendee list transfer directly. Events linked to ZeyOS contacts or deals connect via HubSpot's association model — we create the association records alongside the meeting import.

ZeyOS file records (files table with binfile, filename, mimetype, size) are downloaded, re-uploaded to HubSpot's Files tool, and then attached to the corresponding HubSpot contact, company, or deal record. File URLs change in HubSpot — we document the old ZeyOS file URL in a custom property for traceability.

ZeyOS custom objects map 1:1 to HubSpot custom objects. HubSpot custom objects require pre-creation (name, icon, properties) before migration runs. ZeyOS custom object associations to contacts, companies, or deals translate to HubSpot association labels — we create a HubSpot association type per ZeyOS relationship if the default types do not cover the relationship semantics.

ZeyOS user records are not migrated as contacts. Instead, ZeyOS user email addresses are matched to existing HubSpot users by email. Any ZeyOS owner without a HubSpot user match is flagged — your team either creates HubSpot user accounts first or assigns records to a fallback owner before migration. This prevents records from landing with an unresolvable owner ID.

ZeyOS groups (used for shared calendars, task assignment, and email sharing) have no direct HubSpot CRM equivalent. Group memberships are preserved in a custom property (Original_ZeyOS_Group__c) on each contact or task record for reference. Team-based reporting in HubSpot requires manual setup using HubSpot's user management.