CRM migration
Field-level mapping, validation, and rollback between Workpex and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Workpex
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between Workpex and Nutshell.
Complexity
CModerate
Timeline
2-4 weeks
Overview
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.
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 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
Nutshell
Lead (or Person if contact-type conversion preferred)
1:1Workpex 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
Nutshell
Person
1:1Workpex 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
Nutshell
Account
1:1Workpex 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
Nutshell
Deal
1:1Workpex 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
Nutshell
Activity (Task)
1:1Workpex 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
Nutshell
Activity (Task with reminder flag)
1:manyWorkpex 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
Nutshell
Activity (Call)
1:1Workpex 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
Nutshell
Deal status value
lossyWorkpex 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.
| Workpex | Nutshell | Compatibility | |
|---|---|---|---|
| Lead | Lead (or Person if contact-type conversion preferred)1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Task | Activity (Task)1:1 | Fully supported | |
| Follow-up Reminder | Activity (Task with reminder flag)1:many | Fully supported | |
| Call Record | Activity (Call)1:1 | Fully supported | |
| Pipeline Stage | Deal status valuelossy | 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.
Workpex gotchas
No public API for automated data export
No bulk export mechanism for large datasets
Custom fields and WhatsApp data not visible in standard export
GPS tracking data structure undocumented
Migration timing depends on manual export coordination
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
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.
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.
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.
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.
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
Workpex
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Workpex and Nutshell.
Object compatibility
4 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
Workpex: Not publicly documented.
Data volume sensitivity
Workpex 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 Workpex to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Workpex 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 Workpex
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.