CRM migration

Migrate from ZeyOS to Nutshell

Field-level mapping, validation, and rollback between ZeyOS and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

ZeyOS logo

ZeyOS

Source

Nutshell

Destination

Nutshell logo

Compatibility

67%

8 of 12

objects map 1:1 between ZeyOS and Nutshell.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

ZeyOS logo

ZeyOS

What's pushing teams away

  • Very limited public review presence (only 1 verified G2 review, sparse Capterra coverage) makes it hard for prospective customers to gauge long-term reliability.
  • Smaller vendor footprint compared to Odoo, NetSuite, or HubSpot raises concerns about long-term product support and roadmap stability.
  • Custom iXML scripting layer adds development overhead for teams that want standard integrations without writing custom code.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How ZeyOS objects map to Nutshell

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

maps to

Nutshell

Company

1:1
Fully supported

ZeyOS 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

maps to

Nutshell

Person

1:1
Fully supported

ZeyOS 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

maps to

Nutshell

Lead

1:1
Fully supported

ZeyOS 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

maps to

Nutshell

Opportunity

1:1
Fully supported

ZeyOS 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

maps to

Nutshell

Product

1:1
Fully supported

ZeyOS 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)

maps to

Nutshell

Activity (Call, Email, Meeting, Note)

1:1
Fully supported

ZeyOS 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

maps to

Nutshell

Opportunity + Custom Field

1:many
Fully supported

ZeyOS 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

maps to

Nutshell

Task

many:1
Fully supported

ZeyOS 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

maps to

Nutshell

Lead or Person Custom Field

lossy
Fully supported

ZeyOS 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

maps to

Nutshell

User

1:1
Fully supported

ZeyOS 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

maps to

Nutshell

Custom Fields

lossy
Mapping required

ZeyOS 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)

maps to

Nutshell

Attachment

1:1
Fully supported

ZeyOS 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.

Gotchas + challenges

What specifically takes care here

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 logo

ZeyOS gotchas

High

Audit-locked invoices block post-import edits

High

No documented bulk API forces iterative record-by-record migration

Medium

Unix epoch timestamps require explicit conversion

Medium

File attachments require binary blob download from REST API

Low

Token auth without OAuth limits automation scope

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • ZeyOS invoice audit-lock sequencing must be confirmed before import

    ZeyOS marks invoices as immutable once booked via the API. These cannot be edited or deleted after that point. If invoices are imported out of chronological order, later invoices that reference earlier ones may conflict with ZeyOS's booking sequence. We flag any audit-locked invoices for chronological review with the customer before import begins and sequence invoice imports in strict chronological order. Customers must confirm their invoice chronology during scoping.

  • Unix epoch timestamps require explicit conversion to ISO 8601

    ZeyOS stores creationdate, modification dates, and other timestamps as int8 Unix epoch values (seconds since 1970-01-01). Nutshell's API expects ISO 8601 datetime strings. We explicitly convert each epoch value during the transform step, validate that the resulting dates fall within Nutshell's supported date range, and flag any out-of-range timestamps for customer review before import.

  • File attachments require binary blob download and re-upload per record

    ZeyOS stores file content in the binfile column of the files table. We download binary blobs individually via the REST API, which means no parallelization for attachment retrieval. Large files or attachments with non-standard MIME types may require additional handling. We flag any files exceeding 25MB for customer review before import and note that Nutshell's attachment size limits vary by subscription tier.

  • ERP objects exceed Nutshell's sales CRM scope

    ZeyOS's full data model includes ERP objects (Quotes, Orders, Deliveries, Invoices, Items/Inventory, Projects, Tasks, Tickets, Contracts, Time Entries) that have no direct Nutshell equivalents. We map what we can (Deals to Opportunities, Items to Products, Activities) and flag the remainder as written handoff items for manual migration or a separate ERP system. Customers should confirm which ZeyOS ERP objects are in active use during scoping so we can scope out non-CRM objects before migration begins.

Migration approach

Six steps for a successful ZeyOS to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

ZeyOS logo

ZeyOS

Source

Strengths

  • Unified platform combining CRM, ERP, and Groupware under a single subscription reduces tooling sprawl.
  • Free tier for up to five users enables teams to onboard and evaluate the platform without upfront cost.
  • Open PostgreSQL schema and REST API provide direct database access for migrations and integrations.
  • Audit-proof financial transactions (quotes, orders, invoices) satisfy compliance requirements for locked records.
  • Integrated inventory management with automated stock transactions on every delivery.

Weaknesses

  • Very limited public review presence reduces ability to gauge real-world customer satisfaction and longevity.
  • Smaller market footprint compared to Odoo, NetSuite, or HubSpot raises vendor risk concerns.
  • Custom iXML scripting language creates a learning curve for teams accustomed to standard integration approaches.
  • No documented bulk API means large migrations require iterative record-by-record API calls.
  • Pricing model is primarily per-user, which can become expensive as teams scale beyond 20-30 users.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across ZeyOS and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    ZeyOS: Not publicly documented — we apply exponential backoff on 429/5xx responses and confirm tenant-specific limits during scoping.

  • Data volume sensitivity

    B

    ZeyOS doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your ZeyOS to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about ZeyOS to Nutshell data migrations

Answers to the questions buyers ask most during ZeyOS to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your ZeyOS to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between two and three weeks for CRM-only scopes under 10,000 Contacts and 2,000 Deals. Migrations that include ERP objects (Quotes, Orders, Deliveries, Invoices), large file attachment libraries (over 1,000 files), or custom field-heavy schemas extend to four to six weeks because of per-record API iteration, epoch timestamp conversion, and binary blob handling. The timeline depends on how many ZeyOS object types are actively in use and whether ERP data needs mapping.

Adjacent paths

Related migrations to explore

Ready when you are

Move from ZeyOS.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day