CRM migration
Field-level mapping, validation, and rollback between WORKetc and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
WORKetc
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between WORKetc and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from WORKetc to Nutshell is a downselection from an all-in-one business management platform to a focused CRM. WORKetc bundles CRM, project management, billing, and a help desk under one flat-rate subscription; Nutshell provides contact management, deal tracking, and sales automation without project or invoice modules. We preserve the CRM layer (Contacts, Companies, Deals, Leads, Tickets) using WORKetc's SOAP API with WSDL introspection, and fall back to CSV exports for Starter-tier accounts that lack API access. Project records, weighted stage progress, Invoice headers, and contractor portal users require explicit decisions because Nutshell has no native equivalent. We deliver a written inventory of Workflows, automations, and Knowledge Base articles that must be reconstructed in Nutshell by your admin, because none of these are exposed via WORKetc's API or transferable as structured data.
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 WORKetc 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.
WORKetc
Contact
Nutshell
Person
1:1WORKetc Contact records (name, email, phone, address, lifecycle information) map directly to Nutshell Person. The Nutshell Person API accepts first_name, last_name, email, phone, and address fields directly. Owner assignment migrates by resolving the WORKetc Owner email to the corresponding Nutshell user. Lifecycle stage from WORKetc is preserved as a custom field on the Nutshell Person record for segmentation purposes.
WORKetc
Company
Nutshell
Company
1:1WORKetc Company records map directly to Nutshell Company. The domain from WORKetc's company record populates the Nutshell Company website field. Company-to-Contact relationships are preserved during migration by creating the Company record first, then resolving the company_id on each Contact during Contact import. This ensures the relationship link is satisfied at insert time.
WORKetc
Lead
Nutshell
Lead
1:1WORKetc Lead records (including converted leads with a converted-flag) map to Nutshell Lead. Lead status, source, and any score values migrate as custom fields on the Nutshell Lead record. Leads that were already converted in WORKetc are imported as Persons or Companies in Nutshell depending on the conversion outcome, with the original lead timestamp preserved for audit.
WORKetc
Deal
Nutshell
Deal
1:1WORKetc Deals map to Nutshell Deals with stage, amount, and probability preserved. The WORKetc deal stage maps to a Nutshell pipeline stage. Amount and probability migrate as standard fields. Owner assignment resolves by email match to Nutshell users. Deals are imported after Companies and Persons so that the account relationship and primary contact assignment are satisfied at import time.
WORKetc
Ticket (Support Case)
Nutshell
Lead (as support tracking)
lossyWORKetc Tickets link to Customers, Companies, and Projects with status, priority, and conversation threads. Nutshell does not have a native Case or Ticket object. We map Tickets to Nutshell Leads with a custom field ticket_id__c and a custom status picklist that mirrors the WORKetc ticket stages (New, Open, Pending, Resolved, Closed). Conversation threads migrate as a large text field or as Activity notes linked to the Lead. This is a best-effort structural approximation; if Service Cloud is in scope, Cases would require a separate Service Cloud licensing decision.
WORKetc
Project
Nutshell
No native equivalent
1:1WORKetc Projects with their Types and Stages do not have a native Nutshell equivalent. Nutshell is a CRM without project management capabilities. We export all project records, stage configurations with weights, milestones, and task hierarchies as a structured JSON file and a CSV inventory. The customer uses this to recreate projects in their chosen project management tool (Asana, Monday.com, or similar). We flag which contacts and deals are linked to which projects so that the relationship context is preserved outside the CRM.
WORKetc
Invoice
Nutshell
No native equivalent
1:1WORKetc Invoice headers and line items do not map to Nutshell. We export invoice records (invoice number, date, line items, totals, payment status) as a CSV and JSON inventory. Payment status and linked bank transaction records require separate accounting software reconciliation; WORKetc integrates with Xero and QuickBooks Online, so the customer may already have an accounting tool where invoices should live. We preserve the customer and project linkage on exported invoices for reference.
WORKetc
Custom Field
Nutshell
Custom Field
1:1WORKetc custom field definitions and values migrate to Nutshell custom fields. Field types (dropdown, text, date, number) require mapping to equivalent Nutshell field types. Multi-select dropdowns in WORKetc map to Nutshell multi-value custom fields. Dropdown options migrate as explicit value lists. We validate that migrated custom fields do not conflict with Nutshell's reserved field names before import.
WORKetc
User
Nutshell
User
1:1WORKetc User records (name, email, role, permission level) map to Nutshell users. We resolve users by email match. Any WORKetc User without a matching Nutshell user account is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive WORKetc users migrate as inactive Nutshell users to preserve the owner history on records.
WORKetc
Contractor Portal User
Nutshell
Person (with custom property)
1:1WORKetc Contractor Portal users are a separate identity class with limited access and potentially non-standard email addresses. Nutshell has no contractor portal concept. We map contractor users to Nutshell Person records with a custom field contractor__c set to true, preserving their name and any contact information. Contractor-specific permissions and portal access do not migrate because Nutshell does not support that access model.
| WORKetc | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Ticket (Support Case) | Lead (as support tracking)lossy | Fully supported | |
| Project | No native equivalent1:1 | Fully supported | |
| Invoice | No native equivalent1:1 | Fully supported | |
| Custom Field | Custom Field1:1 | Fully supported | |
| User | User1:1 | Fully supported | |
| Contractor Portal User | Person (with custom property)1: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.
WORKetc gotchas
API access is tier-gated and uses legacy SOAP protocol
Project Types and Stages store weighted progress non-obviously
Contractor portal users are a separate identity class
Stale pricing data on aggregator sites
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 tier verification
We audit the WORKetc account across tier (Starter/Team/Foundations), enabled modules (CRM, Projects, Billing, Tickets, Knowledge Base), custom field definitions, user count, contractor portal users, active workflows, and data volume estimates per object. We verify the current tier from worketc.com/pricing because aggregator sites still show outdated pricing. This output is a written migration scope that explicitly lists which objects migrate, which require custom mapping, and which export as reference data for post-migration rebuild.
API access assessment and export method selection
If the customer is on Starter tier, we confirm API access is unavailable and plan for CSV-based exports from the UI for each object. If the customer is on Team or Foundations, we test SOAP endpoint connectivity via WSDL introspection to discover available methods. We validate export capability for Contacts, Companies, Deals, Tickets, Custom Fields, Projects, and Invoices before designing the migration schema. For any object where API access is unavailable, we prepare UI-based export templates.
Nutshell schema setup and custom field provisioning
We configure Nutshell before any data import. This includes provisioning custom fields to receive WORKetc custom field values, setting up the deal pipeline with stages that mirror the WORKetc deal stages, and creating the contractor__c custom field on Person records. We also configure the ticket_status custom field on Lead records to mirror WORKetc ticket stages for teams using Tickets as support tracking. Custom field types are validated against Nutshell's supported types to avoid import rejections.
Sandbox migration and reconciliation
We run a full migration into a Nutshell trial or sandbox environment using production-like data volume. The customer's point of contact reconciles record counts (Contacts in, Companies in, Deals in, Tickets in), spot-checks 20-40 random records against the WORKetc source, and verifies that company-contact relationships and deal-company links are intact. Mapping corrections happen in this phase. Contractor portal user mapping and custom field type validation are confirmed here.
Production migration in dependency order
We run production migration in record-dependency order: Nutshell users (validated against WORKetc owner emails), Companies (first so they exist as parents), Persons (with company_id resolved), Leads (including converted-lead records), Deals (with account and primary contact resolved), Custom Field values (mapped to provisioned fields), and Ticket records (mapped to Leads with custom status). Projects and Invoices export as structured JSON and CSV reference files rather than Nutshell records. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and rebuild handoff
We freeze WORKetc writes during cutover, run a final delta migration of any records modified during the migration window, then mark Nutshell as the system of record. We deliver the Project and Invoice reference exports, the Workflow and Automation inventory document, and the Knowledge Base content export. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild WORKetc workflows as Nutshell Automations inside the migration scope; that is a separate engagement or an internal admin task.
Platform deep dives
WORKetc
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 WORKetc 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
WORKetc: Not publicly documented. WORKetc does not publish per-minute call limits or response headers indicating remaining quota. We confirm acceptable throughput with WORKetc support before running a full historical export..
Data volume sensitivity
WORKetc 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 WORKetc to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your WORKetc 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 WORKetc
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.