CRM migration
Field-level mapping, validation, and rollback between webCRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
webCRM
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between webCRM and Nutshell.
Complexity
CModerate
Timeline
3-5 weeks
Overview
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.
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 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
Nutshell
Company
1:1webCRM 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
Nutshell
Person
1:1webCRM 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
Nutshell
Deal
1:1webCRM 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
Nutshell
Order (custom object or linked Deal)
1:manywebCRM 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
Nutshell
Product
1:1webCRM 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
Nutshell
Activity
1:1webCRM 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
Nutshell
Custom Field
lossyOrganisations, 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
Nutshell
Workflow (not migrated)
1:1webCRM 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.
| webCRM | Nutshell | Compatibility | |
|---|---|---|---|
| Organisation | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Delivery | Order (custom object or linked Deal)1:many | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Task | Activity1:1 | Fully supported | |
| Custom Field | Custom Fieldlossy | Fully supported | |
| Automation Rule | Workflow (not migrated)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.
webCRM gotchas
Automation rules are not exported or migratable
Export requires manual Overviews navigation
Delivery XML format requires transformation
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
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.
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.
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.
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.
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.
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.
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
webCRM
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 webCRM 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
webCRM: Not publicly documented.
Data volume sensitivity
webCRM 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 webCRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your webCRM 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 webCRM
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.