CRM migration

Migrate from Workpex to Nutshell

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

Workpex logo

Workpex

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

6 of 8

objects map 1:1 between Workpex and Nutshell.

Complexity

CModerate

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Workpex to Nutshell is a migration from a no-API lead management platform into an established SMB CRM with a documented JSON-RPC API. The core challenge is extraction: Workpex has no public API endpoint, no bulk export mechanism, and no published data model for GPS or WhatsApp data, so every object requires a manual export review before we can design the field mapping. We perform a pre-migration audit to identify every custom field, pipeline stage, and activity type present in the account, then coordinate a staged CSV extraction to avoid timeout failures on large datasets. Once data is extracted, we import into Nutshell's People (Contacts) and Accounts (Companies) structure, preserving Workpex's Lead-to-Company relationships as Nutshell Contact-to-Account lookups. Activity history (calls, tasks, notes) lands in Nutshell's shared activity timeline on each Contact and Account record. Follow-up reminders, WhatsApp interaction logs, and GPS data that cannot be mapped natively are flagged for manual review and stored as custom fields or attached documents. Workflows, automations, and WhatsApp marketing sequences do not migrate; we deliver a written inventory of these for your admin to rebuild in Nutshell's automation tools.

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

Workpex logo

Workpex

What's pushing teams away

  • Teams outgrow Workpex when they need advanced pipeline automation, custom objects, or the integrations available in platforms like HubSpot, Salesforce, or Zoho CRM.
  • The lack of a documented public API makes Workpex difficult to integrate with other tools or export data programmatically, driving teams to more open platforms.
  • Customers report that the platform lacks the depth of reporting and analytics available from established CRM competitors, limiting data-driven decision-making.
  • The platform is a smaller vendor with limited market presence, which raises concerns about long-term product support, roadmap stability, and vendor viability.
  • Migrating away from Workpex is painful because there is no standard data export mechanism, making the cost of switching higher than expected.

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 Workpex objects map to Nutshell

Each row shows how a Workpex 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.

Workpex

Lead

maps to

Nutshell

Lead (or Person if contact-type conversion preferred)

1:1
Fully supported

Workpex Leads map directly to Nutshell Leads. The lead's name, email, phone, address, source, and status fields migrate as standard Lead fields. Any custom Lead properties discovered during the pre-migration audit (such as WhatsApp lead source flags or Facebook Ad attribution fields) map to custom Lead fields that we pre-create in Nutshell before import. Workpex's lead assignment to Users maps to the Nutshell Owner field by email match.

Workpex

Contact

maps to

Nutshell

Person

1:1
Fully supported

Workpex Contacts map to Nutshell People. The Contact's name, email, phone, address, and company association migrate as standard People fields. Contact-to-Lead relationships (Workpex links Contacts to Leads) are preserved by importing Leads first and then resolving the Contact's primary Lead association as a custom field or activity note. Note: Nutshell's UI refers to People; the API refers to Contacts. We use the API naming convention throughout migration for consistency.

Workpex

Company

maps to

Nutshell

Account

1:1
Fully supported

Workpex Companies map to Nutshell Accounts. The company name, domain, address, phone, and industry fields migrate as standard Account fields. Account is created before Contact import so that the Account-Contact lookup relationship is satisfied at the moment of Person insert. If Workpex companies have a flat list structure, they map 1:1 to Accounts without transformation.

Workpex

Deal

maps to

Nutshell

Deal

1:1
Fully supported

Workpex Deals map to Nutshell Deals with pipeline stages, monetary value, and expected close dates preserved. Workpex's Deal stage names map to Nutshell Deal status values, and any custom stages are flagged during the pre-migration audit for value-mapping review. Deal assignments to Users map by email match to Nutshell Owner. Deal-to-Company relationships resolve through the Account import phase.

Workpex

Task

maps to

Nutshell

Activity (Task)

1:1
Fully supported

Workpex Tasks map to Nutshell Activities on the Contact or Account record. Task title, due date, status, and assignee migrate. Nutshell's activity timeline groups calls, emails, meetings, and tasks under a single unified view per Person or Account, so Workpex Tasks appear as open to-do items in the timeline and can be checked off directly in Nutshell. Task assignment resolves by email match to the Nutshell User.

Workpex

Follow-up Reminder

maps to

Nutshell

Activity (Task with reminder flag)

1:many
Fully supported

Workpex Follow-up Reminders are tied to Leads or Contacts. Reminder dates and descriptions migrate as Nutshell Activity records with the description field carrying the reminder text and the due date field carrying the reminder timestamp. Multiple reminders for the same Contact merge into separate Activity entries on the shared timeline. If Nutshell's task reminder UI is used, the reminder date maps to the task's follow-up date field.

Workpex

Call Record

maps to

Nutshell

Activity (Call)

1:1
Fully supported

Workpex call tracking metadata (duration, direction, timestamp, disposition) migrates to Nutshell Activity records with call type. The call recording itself migrates as an attachment to the Activity record. Playback format compatibility varies; we flag any recordings in unsupported formats (such as proprietary binary录音 formats) for manual export review before import. Call attribution to the Contact or Account resolves through the email or phone match on the activity's关联 record.

Workpex

Pipeline Stage

maps to

Nutshell

Deal status value

lossy
Fully supported

Workpex pipeline stages are enumerated values on Deals. We map each stage name and its ordering to a Nutshell Deal status value. If Workpex stages include custom labels (such as regional language names or product-specific stages), we flag them during scoping and coordinate with the customer to define equivalent Nutshell status labels before import. Stage ordering in Nutshell's pipeline Kanban view reflects the migration-time stage sequence.

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.

Workpex logo

Workpex gotchas

High

No public API for automated data export

High

No bulk export mechanism for large datasets

Medium

Custom fields and WhatsApp data not visible in standard export

Medium

GPS tracking data structure undocumented

Low

Migration timing depends on manual export coordination

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

  • Workpex has no API; extraction depends on manual CSV coordination

    Workpex does not publish a public API endpoint, authentication mechanism, or bulk export endpoint. We cannot query records programmatically or use any API-based migration approach. Extraction relies on CSV exports from the Workpex UI or direct database access if available on your plan. Large datasets (over 2,000 Leads or Deals) can timeout during UI-based CSV generation. We mitigate this by splitting export requests into batches by object type and date range, validating record counts against UI totals, and recommending a database export from Workpex support if CSV exports are incomplete. Extraction scope is confirmed before migration pricing is finalized.

  • Nutshell's API terminology differs from its UI terminology

    Nutshell's UI refers to People and Companies, but its API uses Contacts and Accounts. The API entityType field returns Contacts and Accounts, not People and Companies. We use the API field names throughout migration to avoid confusion between UI labels and API payloads. Custom fields created in the Nutshell UI are accessible via API using the same API name. If you create custom fields in the UI during migration, confirm the API field name with us before we reference them in import scripts.

  • WhatsApp and GPS data lack documented export formats

    Workpex stores WhatsApp interaction logs and GPS tracking data, but the underlying data model and export formats are not documented. We discover these structures during the pre-migration audit. WhatsApp message text migrates as activity notes on the Contact record, with rich media (images, voice notes) flagged for manual review. GPS location data migrates as custom lat/long fields or coordinates stored as custom fields on the relevant record, pending format validation. Any data that cannot be parsed or mapped from the Workpex export is documented in the pre-migration audit report.

  • Nutshell's activity timeline requires structured date and关联 resolution

    Nutshell's shared activity timeline on People and Accounts requires that each activity record has a valid关联 record (the Person or Account it belongs to) and a valid Owner. If a Workpex activity references a Contact email that does not exist in Nutshell after import, the activity cannot关联 and is held in a reconciliation queue. We resolve activities after all Contacts and Accounts are imported, and we flag any orphaned activities (referencing emails not migrated) for the customer to review and manually associate.

  • Custom fields must be pre-created in Nutshell before import

    Nutshell requires custom fields to exist before data can be imported into them. During the pre-migration audit, we identify every Workpex custom field on Leads, Contacts, Companies, and Deals. We pre-create matching custom fields in Nutshell (using the API) before any record import begins. If custom fields are added to Workpex after migration scoping but before extraction, we update the field map and re-provision in Nutshell before the relevant import phase runs.

Migration approach

Six steps for a successful Workpex to Nutshell data migration

  1. Pre-migration audit and extraction planning

    We audit the Workpex account for every object type, custom field, pipeline stage, user, and activity type present. This includes reviewing the standard CSV export output for each object (Leads, Contacts, Companies, Deals, Tasks, Call Records), identifying any data not visible in the standard export (custom fields, WhatsApp logs, GPS data, Facebook Ad attribution), and estimating file sizes to determine whether batched exports are needed. We deliver a written extraction checklist and coordinate with the customer's Workpex admin to schedule and execute the manual export. If Workpex supports direct database access on the customer's plan, we request a database export instead and validate the schema against the discovered field map.

  2. Destination schema provisioning in Nutshell

    We create every custom field required in Nutshell before any record import begins. Custom fields are provisioned via Nutshell's API using the field names and types from the Workpex discovery phase. Pipeline stages and Deal status values are configured in Nutshell to match the Workpex stage sequence. If the customer uses multiple Workpex pipelines, we create multiple Nutshell Deal lists or use custom fields to distinguish pipeline attribution. We validate the schema in a test import with a subset of records before committing to full production import.

  3. Staged CSV import via Nutshell API

    We import data into Nutshell in dependency order: Accounts (from Workpex Companies) first, then People (from Workpex Contacts and Leads), then Deals (with AccountId and OwnerId resolved), then Activities (Tasks, Call records, Follow-up Reminders). Each object is imported via Nutshell's JSON-RPC API with rate-limit-aware batching. The API rate limits apply primarily to find requests (search queries) rather than add or edit requests, so bulk import operations proceed without throttling. Each phase emits a row-count reconciliation report. Any records rejected during import (due to missing required fields or format errors) are logged and retried after correction.

  4. Activity timeline and association resolution

    After all People and Accounts are loaded, we import activity history. Tasks, Call records, and Follow-up Reminders are associated to the correct Person or Account record using email match, phone match, or Workpex record ID cross-reference. Activities without a valid关联 record are held in a reconciliation queue and reported to the customer for manual review. Call recordings and any large file attachments are uploaded separately and linked to the relevant activity record. We verify the activity timeline order by timestamp to confirm chronological integrity.

  5. Cutover, delta sync, and documentation handoff

    We freeze Workpex writes during the final cutover window and run a delta migration of any records created or modified since the initial extraction. Once Nutshell is confirmed as the system of record, we disable or archive the Workpex account per the customer's preference. We deliver a written inventory of every Workpex object migrated, field mapping document, and any unmigrated data (WhatsApp media files in unsupported formats, GPS data in proprietary formats) with manual recovery instructions. We do not migrate Workpex workflows or automations as code; the inventory document includes a recommended Nutshell automation equivalent for each identified workflow. We support a one-week post-cutover reconciliation window.

Platform deep dives

Context on both ends of the pair

Workpex logo

Workpex

Source

Strengths

  • Consolidates leads, tasks, updates, and deadlines into one platform without requiring multiple tools.
  • Includes built-in call tracking, recording, GPS, and WhatsApp marketing for field sales teams.
  • Simplified interface with minimal configuration overhead for small teams getting started with CRM.
  • Bundled features at a lower price point than enterprise CRM platforms.
  • Follow-up reminders and alerts for stagnant or overdue leads help prevent deals from slipping.

Weaknesses

  • No documented public API limits programmatic data access and makes integrations difficult.
  • Limited market presence and reviews suggest smaller vendor stability concerns.
  • Reporting and analytics depth is shallow compared to established CRM platforms.
  • Lack of advanced automation, custom objects, and workflow capabilities as teams scale.
  • Data portability is essentially non-existent, making migrations painful and manual.
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?

Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

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

  • Object compatibility

    C

    4 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

    Workpex: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Workpex 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 Workpex to Nutshell data migrations

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

Can't find your answer?

Walk through your Workpex 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 four weeks for accounts with under 5,000 Leads, 3,000 Contacts, and 2,000 Deals and no complex custom fields or GPS data. Migrations with large engagement histories (over 50,000 activity records), WhatsApp interaction logs, GPS tracking data, or more than 15 custom fields per object move to four to six weeks because of the pre-migration audit scope, multi-file CSV coordination, and activity-to-timeline transformation work. The primary timeline driver is the manual CSV extraction from Workpex, which requires customer-side coordination and can introduce delays if exports are incomplete or timeout on large datasets.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Workpex.
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