CRM migration

Migrate from webCRM to Nutshell

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

webCRM logo

webCRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

6 of 8

objects map 1:1 between webCRM and Nutshell.

Complexity

CModerate

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from webCRM to Nutshell is a manual-export-first migration because webCRM has no publicly documented API. We guide customers through the Overviews utility to extract Organisations, Contacts, Deals, Products, Tasks, and Deliveries, then transform the nested webCRM Delivery XML from Zynk into tabular Orders and Order Items that import cleanly into Nutshell. The primary data model difference is that webCRM's Organisation-Contact-Deal hierarchy maps directly to Nutshell's Company-Person-Deal structure, but pipeline stage names and custom field labels require individual mapping during the ingestion phase. We flag every active webCRM Automation Module rule during scoping and produce a written inventory for the customer's admin to rebuild in Nutshell because automation logic is not accessible via export. We do not migrate workflows, sequences, or reporting configurations 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

webCRM logo

webCRM

What's pushing teams away

  • Users report support response times as a pain point, with some customers citing delays when resolving configuration issues.
  • As a smaller CRM in a market dominated by HubSpot and Salesforce, businesses scaling beyond 50 users often migrate to platforms with more ecosystem integrations.
  • Limited public API documentation makes the platform difficult to integrate with custom tooling, pushing technical teams toward alternatives with better developer support.

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

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

webCRM

Organisation

maps to

Nutshell

Company

1:1
Fully supported

webCRM Organisations map directly to Nutshell Companies. Organisation name becomes Company name, and any Organisation-level custom fields (industry classification, region, account tier) map to Nutshell Company custom fields. Organisation ID is preserved as an external reference field to support reconciliation during and after migration. We export Organisations first because both Contacts and Deals link to Organisations via ID, and the Company must exist in Nutshell before any dependent records are ingested.

webCRM

Contact

maps to

Nutshell

Person

1:1
Fully supported

webCRM Contacts map to Nutshell People with the Organisation-Contact relationship resolved to the Company-Person relationship via Organisation ID or Organisation name lookup. Contact name, email, phone, address, and role fields map directly to Nutshell Person fields. Any Contact-level custom fields migrate to Nutshell Person custom fields. We export both Organisations and Contacts together to preserve the linkage during ingestion, resolving the Organisation reference before inserting the Person record.

webCRM

Deal

maps to

Nutshell

Deal

1:1
Fully supported

webCRM Deals map to Nutshell Deals with pipeline stage names individually mapped to Nutshell Deal stage values. Deal amount, close date, and owner fields migrate directly. The Organisation link on a webCRM Deal resolves to the Nutshell Company via the Company external reference field. If webCRM Deal stages use custom names not present in Nutshell's default stage set, we create custom stage values in Nutshell before migration to avoid silent mapping failures.

webCRM

Delivery

maps to

Nutshell

Order (custom object or linked Deal)

1:many
Fully supported

webCRM Deliveries are exported in webCRM Delivery XML format via the Zynk connector. The nested XML structure (parent delivery record with line-item detail) requires flattening into two records: an Order header (with delivery date, customer reference, and total) and Order Item rows (with product, quantity, and price). We parse the XML, restructure it into tabular format, and link the Order to the corresponding Company and Deal in Nutshell. Order PDFs attached in webCRM migrate as files linked to the Order record.

webCRM

Product

maps to

Nutshell

Product

1:1
Fully supported

webCRM Product Database records map to Nutshell Products with name, SKU, description, and pricing fields preserved. Product associations to Deals or Deliveries are resolved by matching product ID or name during Order import. If webCRM products include inventory quantities, we map those to a Nutshell custom field because Nutshell Products do not natively track real-time inventory.

webCRM

Task

maps to

Nutshell

Activity

1:1
Fully supported

webCRM Tasks linked to Organisations or Contacts migrate to Nutshell Activities linked to the corresponding Company or Person via external reference resolution. Task subject, description, due date, status, and assignee fields map directly. webCRM task status labels (for example, Open, In Progress, Completed) are mapped to Nutshell Activity status values, and any unmapped labels are preserved in a custom field for admin review.

webCRM

Custom Field

maps to

Nutshell

Custom Field

lossy
Fully supported

Organisations, Contacts, Deals, and other objects in webCRM support custom fields across all objects. We extract the full custom field schema during scoping, identify the data type for each (text, number, date, currency, dropdown), and create equivalent custom fields in Nutshell under the corresponding tab (Company, Person, or Lead). Nutshell supports Text, Long Text, Currency, Date, Dropdown, Checkbox, Number, and URL types. Multi-select picklist fields from webCRM map to Nutshell Dropdown or a custom field type discussion with the customer.

webCRM

Automation Rule

maps to

Nutshell

Workflow (not migrated)

1:1
Fully supported

webCRM Automation Module rules are not accessible via export and cannot be migrated. We identify every active automation during scoping (including time-based triggers, deadline reminders, and inactivity alerts), document each rule's trigger conditions and actions in a written inventory, and deliver that inventory to the customer's admin for rebuild in Nutshell Workflows post-migration. Budget approximately 1-2 hours per automation rule for the rebuild effort.

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.

webCRM logo

webCRM gotchas

High

Automation rules are not exported or migratable

Medium

Export requires manual Overviews navigation

Medium

Delivery XML format requires transformation

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

  • Automation Module rules are not accessible for export

    webCRM stores Automation Module logic internally with no public export endpoint. Any time-based automations, deadline reminders, inactivity triggers, or workflow rules configured in the Automation Module will be lost during migration unless explicitly documented before export. We identify every active automation rule during scoping, produce a written inventory with trigger conditions, action lists, and recommended Nutshell Workflow equivalents, and deliver it to the customer's admin for manual rebuild post-migration. Skipping this step leaves teams without the follow-up sequences and reminder rules they rely on for pipeline hygiene.

  • Export requires manual Overviews navigation with no API

    webCRM has no documented public API for programmatic data extraction. Exports run through the Utilities > Overviews menu, requiring manual navigation to create overview exports for each object type. For large datasets (over 1,000 records per object), multiple export passes are required, and each pass can be time-consuming. We guide customers through the Overviews export process, batch the resulting files into a consistent format, and validate row counts before ingestion begins. If the customer has Zynk configured, we use the Zynk connector for Deliveries XML extraction; otherwise we coordinate a custom export format for order data.

  • webCRM Delivery XML requires flattening before Nutshell import

    webCRM Deliveries are exported in webCRM Delivery XML format via the Zynk connector. The XML structure nests line-item detail within each delivery record, which does not map to any standard Nutshell import format. We parse the XML, flatten the hierarchy into an Order header table and an Order Items child table, and link both to the corresponding Nutshell Company and Deal. Without this transformation step, the nested structure causes import failures or truncated line-item data in Nutshell.

  • Custom field schema differences require pre-migration field creation

    webCRM supports custom fields on Organisations, Contacts, Deals, Products, Tasks, and Deliveries. Nutshell supports custom fields only for Companies, People, and Leads. Any custom fields on webCRM Deals must be recreated in Nutshell Deal custom fields before import. Any custom fields on webCRM Products map to Nutshell Product custom fields. We extract the full custom field schema during scoping, validate the target field types against Nutshell's supported types (Text, Long Text, Currency, Date, Dropdown, Checkbox, Number, URL), and create fields in Nutshell before any records are ingested to avoid silent field rejection during import.

  • Data quality issues (duplicates, incomplete records) propagate into Nutshell

    webCRM datasets accumulated over years commonly contain duplicate Organisation and Contact records, inconsistent address formats, missing email addresses, and stale data from departed users. These quality issues spread into Nutshell during migration if not addressed beforehand. We run a pre-migration data quality audit identifying duplicates (matched on Organisation name and email), incomplete records missing required fields, and inconsistent formats (phone number structures, address components). The customer decides whether to clean data before migration or import as-is with a deduplication plan for post-migration cleanup.

Migration approach

Six steps for a successful webCRM to Nutshell data migration

  1. Scoping and data quality audit

    We audit the webCRM account by guiding the customer through the Overviews export for each object type (Organisations, Contacts, Deals, Products, Tasks, Deliveries). We extract record counts, identify active Automation Module rules, document the custom field schema, and assess data quality (duplicate density, incomplete record rates, and format consistency). The scoping output is a written migration scope document including object counts, field mapping table, automation inventory, and a data quality report with cleaning recommendations.

  2. Delivery XML transformation design

    For webCRM Deliveries exported via Zynk in XML format, we design the flattening transform before any data moves. The transformation parses the nested Delivery XML, extracts header fields (delivery date, customer reference, total amount) into an Order record, and extracts line-item detail into Order Items linked by a shared Order ID. We test the transform against a sample of 10-20 Deliveries to validate that all line-item fields (product, quantity, unit price, discount) are preserved in the flattened structure before running the full extraction.

  3. Nutshell custom field and stage configuration

    We create the required custom fields in Nutshell before record ingestion. This includes Company custom fields (mapped from Organisation custom fields), Person custom fields (mapped from Contact custom fields), Deal custom fields (mapped from Deal custom fields), and Product custom fields (mapped from Product custom fields). If webCRM uses custom Deal stage names not present in Nutshell's default stages, we create custom stage values in Nutshell Deal pipeline configuration. Nutshell is configured in the customer's live environment with a migration hold on record creation until field schema is confirmed.

  4. Company and Product ingestion

    We ingest Organisations (as Companies) and Products first because both Contacts and Deals link to Companies, and Order Items link to Products. Organisation IDs are stored as an external reference field on each Nutshell Company for lookup resolution during subsequent phases. Product names and SKUs are matched to ensure Order Items resolve correctly during the Deliveries phase. We validate row counts against the source Overviews export before proceeding.

  5. Person and Deal migration with relationship resolution

    We ingest Contacts as People, resolving each Person's Organisation link to the corresponding Nutshell Company via the external reference field. We then ingest Deals, resolving each Deal's Organisation link to the Company and assigning the correct Deal stage from the pre-configured stage mapping. The Deal-Deal link (if Deals reference other Deals) is held for resolution after initial Deal ingestion completes. Any Deal-level custom fields are populated during this phase.

  6. Deliveries ingestion as Orders

    We run the Zynk XML extraction for Deliveries, apply the flattening transformation, and ingest the resulting Order header records first. We then ingest Order Items linked to each Order and to the corresponding Product via SKU or name lookup. Order total is validated against the original Delivery XML before the Order is marked complete. Any Delivery attachments migrate as files linked to the Order record.

  7. Cutover, delta sync, and automation handoff

    We freeze writes in webCRM during the final 48-hour delta window, migrate any records modified since the initial extraction, then confirm the cutover to Nutshell as the system of record. We deliver the Automation Module inventory document to the customer's admin team for rebuild in Nutshell Workflows. We support a one-week hypercare window resolving any record reconciliation issues raised by the sales team. Workflow rebuild, sequence configuration, and admin training are outside standard migration scope and are handled as separate engagements.

Platform deep dives

Context on both ends of the pair

webCRM logo

webCRM

Source

Strengths

  • Pipeline management with customisable stages and revenue forecasting
  • Product database with real-time inventory overview
  • Task and time-based automation for follow-ups and reminders
  • Order management linking quotes to deliveries and inventory
  • High customer support ratings (4.7/5) on review platforms

Weaknesses

  • No publicly documented API for direct programmatic access
  • Automation rules are not exportable and must be rebuilt manually
  • Smaller market footprint limits third-party integrations compared to major CRMs
  • Export relies on manual Overviews utility or third-party tools like Zynk
  • Limited pricing transparency makes cost comparison difficult
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 webCRM 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

    webCRM: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your webCRM 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 three and five weeks for accounts under 5,000 Contacts, 2,000 Organisations, and 1,000 Deals with straightforward field mapping and no extensive custom field schema. Migrations with high Deliveries volume (over 500 order records with nested XML requiring flattening), extensive custom field schemas (over 30 custom fields across objects), or multiple active automation rules requiring full inventory documentation move to six to ten weeks because of the transformation design work and the manual export coordination required for each object type.

Adjacent paths

Related migrations to explore

Ready when you are

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