CRM migration
Field-level mapping, validation, and rollback between ZeyOS and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
ZeyOS
Source
Nutshell
Destination
Compatibility
8 of 12
objects map 1:1 between ZeyOS and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from ZeyOS to Nutshell is a narrowing migration: ZeyOS bundles CRM, ERP, and Groupware into a single platform, while Nutshell is a purpose-built sales CRM for small and mid-market teams. We extract ZeyOS's Accounts, Contacts, Leads, Deals, and Activities from the REST API and map them into Nutshell's Companies, People, Leads, and Opportunities. ZeyOS's ERP objects (Quotes, Orders, Deliveries, Invoices, Items, Projects, Tasks, Tickets, Contracts, Time Entries) exceed Nutshell's scope; we migrate them as a best-effort mapping with a written inventory of unmapped ERP records for your admin to handle manually or in a separate system. Financial transactions marked audit-locked in ZeyOS are flagged for chronological review before import to prevent locked-record conflicts. We do not migrate ZeyOS Workflows, Sequences, or custom iXML scripts as code.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a ZeyOS object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
ZeyOS
Account
Nutshell
Company
1:1ZeyOS Account records map directly to Nutshell Company records. The Account's name, address fields, phone, and website transfer to the corresponding Company fields. We use Account name as the dedupe key during import and create Company records before any Person import so that the People-to-Company relationship is satisfied at insert time.
ZeyOS
Contact
Nutshell
Person
1:1ZeyOS Contact records map to Nutshell Person records with the parent-Account relationship preserved as the link to the Company. The Contact's name, email, phone, and address fields transfer directly. We resolve the parent Account FK to the Nutshell Company record by name match during migration. ZeyOS extdata fields (nickname, additional addresses) map to Person custom fields where Nutshell supports them.
ZeyOS
Lead
Nutshell
Lead
1:1ZeyOS Lead records map to Nutshell Lead records. Lead-specific status fields from ZeyOS (lead stage, source, rating) transfer to Nutshell Lead custom fields or standard fields where the field names align. If the customer uses ZeyOS Leads differently from Contacts, we preserve the distinction in Nutshell Lead without merging.
ZeyOS
Deal
Nutshell
Opportunity
1:1ZeyOS Deal records map to Nutshell Opportunity. The deal amount, close date, and deal name transfer to Nutshell's opportunity fields. We map ZeyOS pipeline and stage to Nutshell's pipeline configuration and validate that stage names are supported values in the destination. Deal-owner resolution is by email match to Nutshell Users.
ZeyOS
Items
Nutshell
Product
1:1ZeyOS Items (inventory/product catalog) map to Nutshell Product records. We transfer the item name, barcode, SKU, model, and unit price. Stock quantities from ZeyOS's automated inventory transactions do not map to Nutshell because Nutshell lacks native inventory management; we flag these as a written note for the customer's admin to manage in a separate inventory tool post-migration.
ZeyOS
Activity (Call, Email, Meeting, Note)
Nutshell
Activity (Call, Email, Meeting, Note)
1:1ZeyOS Activity records (calls, emails, meetings, notes) linked to Accounts or Contacts map to Nutshell Activity records attached to the corresponding Company or Person. We convert ZeyOS int8 Unix timestamps to ISO 8601 datetime strings during transform. Activity owner resolution is by email match. Note body content transfers as the activity description.
ZeyOS
Quote, Order, Delivery, Invoice
Nutshell
Opportunity + Custom Field
1:manyZeyOS financial documents (Quotes, Orders, Deliveries, Invoices) have no direct Nutshell equivalents. We map Quote and Order metadata to the parent Opportunity as custom fields and flag the records for manual review. Audit-locked Invoices (immutable post-booking in ZeyOS) are flagged separately with a chronological ordering warning to prevent import conflicts. Deliveries are noted as a written handoff item for the customer's admin.
ZeyOS
Project, Task, Time Entry
Nutshell
Task
many:1ZeyOS Projects, Tasks, and Time Entries have no direct Nutshell equivalents. We merge the highest-level Task per Project into Nutshell Task records attached to the parent Company or Person, preserving the task name, assignee, due date, and status. Time entry hours are stored as a custom Task field. We flag Projects as a written handoff because Nutshell lacks native project management. Customer admins review the task merge and determine whether a separate project tool is needed post-migration.
ZeyOS
Ticket
Nutshell
Lead or Person Custom Field
lossyZeyOS Tickets (Helpdesk object with email integration) have no direct Nutshell equivalent. We map ticket subject, status, priority, and conversation threads as a custom field set on the linked Person or Company, or as a Lead with ticket-type custom fields. Email thread history migrates as Note records attached to the Person. We recommend the customer configure a helpdesk integration (Zendesk, Freshdesk) post-migration if ongoing ticket management is required.
ZeyOS
User
Nutshell
User
1:1ZeyOS Users map to Nutshell Users by email match. We extract every distinct ZeyOS User referenced on Contacts, Accounts, Deals, and Activities and match against Nutshell's User table. Any ZeyOS User without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes.
ZeyOS
Custom Fields
Nutshell
Custom Fields
lossyZeyOS custom fields (fields table and extdata JSON) are read and mapped to Nutshell custom fields on the corresponding object (Company, Person, Lead). Nutshell supports Text, Long Text, Currency, and Date custom field types; we map ZeyOS field types to the closest Nutshell equivalent. Custom field definitions are created in Nutshell before data import begins. Fields without a compatible Nutshell type are flagged in the mapping document for manual handling.
ZeyOS
Documents (File Attachments)
Nutshell
Attachment
1:1ZeyOS file attachments (binfile column binary blobs) are retrieved individually via the REST API and re-uploaded to Nutshell as attachments on the corresponding Company, Person, or Opportunity record. We resolve the file's parent record FK during retrieval and attach by record ID in Nutshell. Files exceeding 25MB are flagged for customer review before import because Nutshell has attachment size limits that vary by plan.
| ZeyOS | Nutshell | Compatibility | |
|---|---|---|---|
| Account | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Items | Product1:1 | Fully supported | |
| Activity (Call, Email, Meeting, Note) | Activity (Call, Email, Meeting, Note)1:1 | Fully supported | |
| Quote, Order, Delivery, Invoice | Opportunity + Custom Field1:many | Fully supported | |
| Project, Task, Time Entry | Taskmany:1 | Fully supported | |
| Ticket | Lead or Person Custom Fieldlossy | Fully supported | |
| User | User1:1 | Fully supported | |
| Custom Fields | Custom Fieldslossy | Mapping required | |
| Documents (File Attachments) | Attachment1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
ZeyOS gotchas
Audit-locked invoices block post-import edits
No documented bulk API forces iterative record-by-record migration
Unix epoch timestamps require explicit conversion
File attachments require binary blob download from REST API
Token auth without OAuth limits automation scope
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and object inventory
We audit the ZeyOS instance via the REST API to inventory all object types in use: Accounts, Contacts, Leads, Deals, Items, Activities, Tickets, Projects, Tasks, Contracts, and any financial documents (Quotes, Orders, Deliveries, Invoices). We count records per object, flag custom field definitions from the fields table, identify file attachment volume, and note which ZeyOS ERP objects are actively used versus legacy. This scoping output determines whether the migration is CRM-only or includes ERP objects and informs the pricing estimate.
Schema mapping and custom field creation
We map each ZeyOS object to its Nutshell equivalent and design the custom field schema. For each ZeyOS custom field, we identify the closest Nutshell field type (Text, Long Text, Currency, Date) or flag it as requiring a manual workaround. We create Nutshell custom fields via the API before any data import. ERP objects that cannot map to Nutshell are documented in the mapping specification as manual handoff items.
Timestamp conversion and file attachment preparation
We run a transform pass over the exported ZeyOS data to convert int8 Unix epoch timestamps to ISO 8601 datetime strings. We validate date ranges and flag out-of-range timestamps. For file attachments, we download binary blobs from the files table individually and prepare them for re-upload to Nutshell with the correct MIME type and parent record reference. Files exceeding 25MB are flagged separately.
Owner reconciliation and User provisioning
We extract every distinct ZeyOS User referenced on Accounts, Contacts, Deals, Activities, and Tickets and match by email against Nutshell's User table. Any ZeyOS User without a matching Nutshell User goes to a reconciliation queue. The customer's admin provisions missing Users in Nutshell before record import begins. Owner resolution must be complete because OwnerId references are required on most standard records.
Production migration in dependency order
We run production migration in record-dependency order: Users (provisioned and validated), Companies (from ZeyOS Accounts), People (from ZeyOS Contacts, with CompanyId resolved), Leads, Opportunities (from ZeyOS Deals with pipeline and stage mapped), Products (from ZeyOS Items), Activities (via REST API with timestamp conversion applied), file attachments (uploaded per-record), and finally any mapped ERP metadata as Opportunity custom fields. Each phase emits a row-count reconciliation report before the next begins.
Cutover, validation, and handoff
We freeze ZeyOS writes during cutover and run a final delta migration of any records modified during the migration window. We deliver the mapping specification including any unmapped ERP objects, file attachment logs, and timestamp conversion reports. We support a one-week hypercare window for reconciliation issues. We do not rebuild ZeyOS Workflows, Sequences, or iXML scripts in Nutshell; those are documented separately for the customer's admin to rebuild as Nutshell automation rules.
Platform deep dives
ZeyOS
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across ZeyOS and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
ZeyOS: Not publicly documented — we apply exponential backoff on 429/5xx responses and confirm tenant-specific limits during scoping.
Data volume sensitivity
ZeyOS doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during ZeyOS to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your ZeyOS to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave ZeyOS
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.