CRM migration

Migrate from Divalto weavy to Nutshell

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

Divalto weavy logo

Divalto weavy

Source

Nutshell

Destination

Nutshell logo

Compatibility

78%

7 of 9

objects map 1:1 between Divalto weavy and Nutshell.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Divalto weavy to Nutshell addresses two structural limitations that compound over time: Divalto weavy has no publicly documented REST API, forcing all integrations and exports through Zapier with no bulk data capability, while Nutshell offers a documented REST API with custom fields for Companies, People, and Leads available from its entry tier. The migration begins with a vendor-coordinated full data export from Divalto weavy because no direct API read is possible, followed by a schema audit of any Development Studio custom objects and fields that require explicit mapping to Nutshell's typed custom field model. We preserve activity history (calls, meetings, tasks, notes) by mapping to Nutshell's Activities tied to People and Companies, and we resolve owner assignments via email lookup in Nutshell's Users table. We do not migrate route and itinerary data, Workflows, or custom automations built in the Divalto Development Studio; these are documented for the customer's admin to rebuild in Nutshell's native tools post-migration.

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

Divalto weavy logo

Divalto weavy

What's pushing teams away

  • Pricing is consistently cited as a downside in French reviews — entry rate from €40/user/month with no free plan, which is steep for VSEs (very small enterprises).
  • No free or freemium tier, so evaluation requires a paid commitment or sales-led demo rather than self-serve trial.
  • Outside France/French-speaking Europe the support and integrator network is thin, limiting adoption for multinational rollouts.
  • Focus on SME/mid-market means very small startups and global enterprises both fall outside the natural fit zone.
  • Catalog website mismatch (weavy.com is a different product) makes vendor identification harder for international buyers — the actual product lives at divalto.com.

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

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

Divalto weavy

Company

maps to

Nutshell

Company

1:1
Fully supported

Divalto weavy Company records map to Nutshell Company. We extract the company name, industry classification, billing and shipping addresses, and any custom fields defined in the Development Studio. The company name becomes the Nutshell Company name and the primary dedupe key. Development Studio custom fields on Company migrate as Nutshell custom fields created under Settings > Customize Fields > Companies before import.

Divalto weavy

Contact

maps to

Nutshell

Person

1:1
Fully supported

Divalto weavy Contact records map to Nutshell Person. Standard fields (name, email, phone, title, address) migrate directly. Divalto weavy profile assignments (Standard, Sales, Technician, Full) are preserved in a Nutshell custom field profile__c for reference. Development Studio custom properties on Contact require pre-migration field creation in Nutshell and explicit mapping during the import phase.

Divalto weavy

Lead

maps to

Nutshell

Lead

1:1
Fully supported

Divalto weavy leads (suspect-to-prospect-to-client lifecycle) map to Nutshell Lead. Lead status and source attribution fields migrate to Nutshell's lead status and source picklist fields. If the customer uses Nutshell's People-first model where all prospects enter as Person records rather than separate Leads, we merge at migration time based on the customer's preference established during scoping.

Divalto weavy

Deal

maps to

Nutshell

Account

lossy
Fully supported

Divalto weavy Deals represent revenue-generating opportunities tied to pipeline stages. In Nutshell, Deals attach to Company records. We map the deal name to a Nutshell Deal name, deal value to Amount, expected close date to Close Date, and the Divalto pipeline stage to a Nutshell pipeline stage. If the customer uses Nutshell's CRM Classic model, Deals migrate as Nutshell Deal records; if using CRM Classic with Accounts, we map to the Account object.

Divalto weavy

Pipeline Stage

maps to

Nutshell

Pipeline Stage

lossy
Fully supported

Divalto weavy configurable pipeline stages map to Nutshell pipeline stages. We extract the full stage list during discovery, including any custom stage names, and configure matching Nutshell pipeline stages before migration. Probability weights from Divalto weavy map to Nutshell stage probability percentages.

Divalto weavy

Activity

maps to

Nutshell

Activity

1:1
Fully supported

Divalto weavy Activities (calls, meetings, action items linked to contacts or deals) map to Nutshell Activities tied to the corresponding Person and Company. Activity type, date, description, and owner transfer directly. Activity history is migrated in full to preserve the customer interaction timeline for the sales team. The Nutshell REST API handles the activity insert with parent-record lookup resolution.

Divalto weavy

User/Team Member

maps to

Nutshell

User

1:1
Fully supported

Divalto weavy user profiles (Standard, Sales, Technician, Full) map to Nutshell User records via email match. Divalto weavy profile assignment is stored in a custom field on the mapped Nutshell User record. Any Divalto weavy user without a matching Nutshell User goes to a reconciliation queue for the customer admin to provision before record import resumes.

Divalto weavy

Attachment

maps to

Nutshell

File (via Note or attachment)

1:1
Fully supported

Divalto weavy document attachments linked to companies, contacts, and deals are extracted and mapped to Nutshell's attachment model. Files attach to the correct parent record (Company or Person) and preserve the original filename and upload date. If Nutshell's file attachment limit is a concern, we discuss archiving larger files to a cloud storage link referenced in the record.

Divalto weavy

Custom Object (Development Studio)

maps to

Nutshell

Custom Object

1:1
Fully supported

Divalto weavy Development Studio custom objects and their field definitions have no standard export mechanism. We conduct a pre-migration schema audit in the source environment, cataloguing every custom object and field definition manually, then pre-create equivalent custom fields in Nutshell under the relevant object (Company, Person, or Lead) before data import begins. Mapping rules are documented explicitly for each custom field with its source type, destination type, and any transformation logic.

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.

Divalto weavy logo

Divalto weavy gotchas

High

No public API documentation for direct migration

Medium

Per-user pricing model inflates cost with headcount

Medium

Development Studio customizations are non-standard and require explicit mapping

Low

Route and itinerary data has no destination equivalent

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

  • No public API requires vendor-coordinated manual export

    Divalto weavy does not publish a public REST API reference. We cannot perform direct API-based reads or writes to the source platform. We work around this by requesting full data exports from the Divalto weavy vendor portal or by coordinating manual CSV exports from within the platform. This adds steps and dependencies on vendor responsiveness during the migration project, and the customer must ensure their Divalto vendor can provide a complete, up-to-date export before migration begins.

  • Development Studio custom fields require manual pre-audit

    Organizations with custom objects or custom fields built in the Divalto weavy Development Studio have non-standard schemas that vary per tenant. There is no documented schema registry or export of custom field definitions. We handle this by running a pre-migration schema audit in the source environment, manually cataloguing every custom object and field, and applying explicit field-level mapping rules before any data is loaded into Nutshell. This phase can add one to two weeks to the project timeline compared to migrations with no custom objects.

  • Route and itinerary data has no Nutshell equivalent

    Divalto weavy's route planning and itinerary data are designed for mobile field workers and have no standard equivalent in Nutshell. If this data is business-critical, customers must decide whether to export it as a standalone report before cutover. We flag this gap during the scoping call, offer a manual export workflow as an optional add-on, and do not include route data in the standard migration package.

  • Activity history transfer depends on export completeness

    Because Divalto weavy has no bulk export API, activity history (calls, meetings, tasks, notes) must be included in the vendor-assisted data export. If the export omits activity records or truncates long text fields, those gaps appear in Nutshell. We validate the export scope during discovery and request a sample of activity records before committing to the full migration volume. Any missing activity records after cutover cannot be retrofilled without a second export request from Divalto weavy.

Migration approach

Six steps for a successful Divalto weavy to Nutshell data migration

  1. Discovery and export coordination

    We conduct a scoped discovery session with the customer to identify the full record inventory in Divalto weavy: company count, contact count, deal count, activity volume, attachment volume, user count, and any Development Studio custom objects or fields. Because no direct API read is available, we also coordinate with the Divalto weavy vendor to request a full data export in CSV or another accessible format. We assess export completeness during this phase and flag any gaps before proceeding.

  2. Schema audit for Development Studio customizations

    If the customer uses Development Studio custom objects or custom fields, we perform a manual schema audit in the source environment, cataloguing every custom field definition, its data type, and its parent object. We then pre-create equivalent custom fields in Nutshell under the relevant object (Company, Person, or Lead) using Nutshell's Settings > Customize Fields interface, and we document the explicit mapping rule for each field before any data is loaded.

  3. Owner and user reconciliation

    We extract every distinct Divalto weavy user referenced on Companies, Contacts, Deals, and Activity records and match by email against the Nutshell destination's User table. Any Divalto weavy user without a matching Nutshell User goes to a reconciliation queue. The customer admin provisions missing Nutshell Users before record import resumes, because OwnerId references are required on most standard object inserts.

  4. Sandbox migration and reconciliation

    We run a full migration into Nutshell using a test account or a non-production environment if available. The customer reviews the migrated record counts, spot-checks 20-30 random records against the Divalto weavy source, and signs off on the schema and mapping before production migration begins. Any mapping corrections or missing fields are addressed in this phase.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Nutshell Users (validated), Companies (from Divalto weavy Company records), Persons (from Divalto weavy Contact records with AccountId resolved), Leads (if using separate Lead model), Deals (with CompanyId, OwnerId, and Pipeline Stage resolved), Activities (via Nutshell REST API with parent-record lookup), Attachments (mapped to the correct parent Company or Person). Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and documentation handoff

    We freeze writes in Divalto weavy during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver a written inventory of all Development Studio custom fields that require rebuild in Nutshell's native custom field tools, and we note any Workflow equivalents that the customer's admin should implement in Nutshell's automation layer. We support a 48-hour hypercare window for reconciliation issues. We do not rebuild Divalto weavy automations or Development Studio workflows as Nutshell automations inside the migration scope.

Platform deep dives

Context on both ends of the pair

Divalto weavy logo

Divalto weavy

Source

Strengths

  • Mobile CRM with offline mode for itinerant salespeople working without reliable connectivity
  • Route optimization and geocoding built natively into the mobile workflow
  • Open application architecture with a Development Studio for custom objects and workflows
  • Direct ERP connectivity to Divalto Business, Divalto Field Service, and Divalto Industry via the Divalto marketplace
  • Per-user pricing at €40/month with profile-based access control (Standard, Sales, Technician, Full)

Weaknesses

  • No publicly documented API; integrations rely on Zapier with no native bulk export capability
  • Pricing is opaque for anything beyond the base per-user rate; options like the development studio require contacting sales
  • Scarce English-language documentation and limited third-party review coverage outside French-language sources
  • Fewer than 10 verified reviews across major review platforms makes peer assessment difficult
  • No free trial available, increasing commitment risk before full evaluation
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 Divalto weavy 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

    Divalto weavy: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your Divalto weavy 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 5,000 contacts, 1,000 companies, and no Development Studio custom objects. Migrations with Development Studio custom objects, large activity histories (over 50,000 records), or multi-profile user structures move to five to eight weeks because of the manual schema audit, vendor export coordination, and explicit field-level mapping required before any data loads.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Divalto weavy.
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