CRM migration
Field-level mapping, validation, and rollback between Divalto weavy and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Divalto weavy
Source
Nutshell
Destination
Compatibility
7 of 9
objects map 1:1 between Divalto weavy and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
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.
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 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
Nutshell
Company
1:1Divalto 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
Nutshell
Person
1:1Divalto 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
Nutshell
Lead
1:1Divalto 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
Nutshell
Account
lossyDivalto 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
Nutshell
Pipeline Stage
lossyDivalto 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
Nutshell
Activity
1:1Divalto 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
Nutshell
User
1:1Divalto 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
Nutshell
File (via Note or attachment)
1:1Divalto 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)
Nutshell
Custom Object
1:1Divalto 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.
| Divalto weavy | Nutshell | Compatibility | |
|---|---|---|---|
| Company | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Deal | Accountlossy | Fully supported | |
| Pipeline Stage | Pipeline Stagelossy | Fully supported | |
| Activity | Activity1:1 | Fully supported | |
| User/Team Member | User1:1 | Fully supported | |
| Attachment | File (via Note or attachment)1:1 | Fully supported | |
| Custom Object (Development Studio) | Custom Object1: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.
Divalto weavy gotchas
No public API documentation for direct migration
Per-user pricing model inflates cost with headcount
Development Studio customizations are non-standard and require explicit mapping
Route and itinerary data has no destination equivalent
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 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.
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.
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.
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.
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.
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
Divalto weavy
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 Divalto weavy 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
Divalto weavy: Not publicly documented.
Data volume sensitivity
Divalto weavy 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 Divalto weavy to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Divalto weavy
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.