CRM migration

Migrate from WORKetc to Nutshell

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

WORKetc logo

WORKetc

Source

Nutshell

Destination

Nutshell logo

Compatibility

90%

9 of 10

objects map 1:1 between WORKetc and Nutshell.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

WORKetc logo

WORKetc

What's pushing teams away

  • Teams outgrow the platform as they scale — one reviewer noted the product worked initially but they quickly outgrew it.
  • Email integration limitations frustrate users who rely on direct synchronization with third-party email services.
  • Bugs and difficulty customizing the platform appear in negative reviews, particularly around early use periods.
  • The $78+ flat rate becomes expensive per-user as headcount grows beyond the included seats on Starter.
  • Some users report that the interface feels less polished than newer CRM competitors entering the market.

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

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

maps to

Nutshell

Person

1:1
Fully supported

WORKetc 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

maps to

Nutshell

Company

1:1
Fully supported

WORKetc 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

maps to

Nutshell

Lead

1:1
Fully supported

WORKetc 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

maps to

Nutshell

Deal

1:1
Fully supported

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

maps to

Nutshell

Lead (as support tracking)

lossy
Fully supported

WORKetc 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

maps to

Nutshell

No native equivalent

1:1
Fully supported

WORKetc 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

maps to

Nutshell

No native equivalent

1:1
Fully supported

WORKetc 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

maps to

Nutshell

Custom Field

1:1
Fully supported

WORKetc 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

maps to

Nutshell

User

1:1
Fully supported

WORKetc 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

maps to

Nutshell

Person (with custom property)

1:1
Fully supported

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

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.

WORKetc logo

WORKetc gotchas

High

API access is tier-gated and uses legacy SOAP protocol

Medium

Project Types and Stages store weighted progress non-obviously

Medium

Contractor portal users are a separate identity class

Low

Stale pricing data on aggregator sites

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

  • Starter-tier accounts have no API access

    WORKetc's Starter plan ($78/month) does not include the Open API module. Teams on Starter cannot export data programmatically at all. Even on higher tiers, WORKetc's API is SOAP-first with REST/JSON wrappers added later. We handle SOAP serialization using WSDL introspection to discover available methods. For Starter accounts, we fall back to CSV exports from the UI for Contacts, Companies, Deals, and Tickets, and manual exports for custom fields. We always verify the customer's current tier from worketc.com/pricing before scoping, because multiple review aggregators still show outdated pricing.

  • Project Types and Stages do not map to any Nutshell object

    WORKetc's Project Types and Stages feature uses custom percentage weights per stage — a two-task project could have 'Do Work' at 90% and 'Review' at 10%, which is non-linear and non-standard. This weighted progress data has no equivalent in Nutshell, which has no project management module at all. We export the full stage configuration including weights and deliver it as a structured JSON reference file. The customer uses this to rebuild projects in a dedicated project management tool. Progress data in Nutshell must be tracked manually or via an external tool.

  • Nutshell has no invoice or billing module

    WORKetc's Invoice module (headers, line items, payment status, linked bank records) has no Nutshell equivalent. We export invoice data as structured CSV and JSON, but the customer must decide whether invoices should live in a separate accounting tool (Xero, QuickBooks Online, or WORKetc's existing integrations). We preserve the customer and project linkage in the export so that invoice context is not lost even if the invoice records themselves do not migrate into Nutshell.

  • Contractor portal users require identity remapping

    WORKetc distinguishes between full Users and Contractor Portal users with different permission scopes. Contractor records may lack standard email addresses or user credentials. When migrating to Nutshell without a contractor portal, we map contractor users to Contact records with a custom contractor flag. Contractor-specific permissions and portal access do not transfer because Nutshell does not support that access model. The customer's admin should review contractor Contact records post-migration to ensure appropriate Nutshell user access if contractors need CRM visibility.

  • WORKetc workflows and automations are not exposed via API

    WORKetc workflow rules, automation triggers, and the Knowledge Base article system are not accessible via the SOAP or REST API. These must be reconstructed manually in Nutshell using exported descriptions as reference. We deliver a written inventory of every active WORKetc workflow and automation with its trigger conditions, actions, and recommended Nutshell equivalent (email sequences, lead routing rules, task automations). The Knowledge Base articles export as structured content for the customer to recreate in a knowledge base tool of their choice.

Migration approach

Six steps for a successful WORKetc to Nutshell data migration

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

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

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

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

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

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

Context on both ends of the pair

WORKetc logo

WORKetc

Source

Strengths

  • Flat-rate pricing bundles CRM, project management, and billing in one subscription.
  • Configurable Project Types and Stages give weighted progress tracking for complex service engagements.
  • Customer portal and contractor portal provide self-service access for external stakeholders.
  • Strong Capterra ratings (4.6/5) with 94% positive sentiment and praised customer support.
  • Two-way Google Calendar and Contact Sync keeps Google Workspace users' data current.

Weaknesses

  • SOAP-first API is dated; REST/JSON support exists but documentation is thin and developer-focused.
  • API access itself is gated behind paid tiers — Starter excludes Open API entirely.
  • Project Types and Stages progress system is non-standard and requires mapping work in migrations.
  • Small review sample (85 reviews on Capterra) limits confidence in long-term reliability signals.
  • Alternatives like Zoho CRM, Odoo, and Bitrix24 offer more integrations and larger ecosystem communities.
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 WORKetc 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

    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

    B

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

Estimator

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

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

Can't find your answer?

Walk through your WORKetc 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 under 10,000 Contacts and 2,000 Deals with no custom field complexity and no contractor portal records. Migrations with Project record exports, weighted stage progress conversion, large Ticket histories (over 5,000 cases), or multiple custom field definitions move to six to ten weeks because of the schema work, SOAP serialization handling, and post-migration rebuild documentation scope. Starter-tier accounts may take longer because API access is unavailable and CSV exports require manual preparation per object.

Adjacent paths

Related migrations to explore

Ready when you are

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