CRM migration
Field-level mapping, validation, and rollback between Onsite CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Onsite CRM
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between Onsite CRM and Nutshell.
Complexity
CModerate
Timeline
1-3 weeks
Overview
Moving from Onsite CRM to Nutshell is a CSV-first migration because Onsite CRM has no documented REST API, no SDK, and no webhook infrastructure according to apitracker.io. All data extraction relies on in-app CSV exports, which requires careful scoping to confirm what objects and fields the UI exposes at the customer's account. We map Onsite CRM's contact, company, deal, and activity records into Nutshell's People, Organizations, Deals, and Activity Timeline, resolving the company-contact relationship through Nutshell's organization association field. Pipeline stages map to Nutshell pipeline stages with order and probability preserved where supported. Custom fields require manual field-by-field mapping during scoping because Onsite CRM's custom field structure varies by customer configuration and Nutshell's custom field limits are plan-dependent (Foundation limits are more restrictive than Pro or Enterprise). Workflows, automations, and sequences do not migrate; we deliver a written inventory of any outbound activity configurations requiring rebuild in Nutshell's automation tools.
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 Onsite CRM 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.
Onsite CRM
Contact
Nutshell
People
1:1Onsite CRM Contact records export via in-app CSV with fields including name, email, phone, and company association. We map these directly to Nutshell People records using the email address as the dedupe key. The company association from Onsite CRM resolves to a Nutshell Organization via the organization's name match on import. Any custom properties on the Contact record are flagged for field-by-field mapping during scoping because Onsite CRM's custom field structure varies by customer configuration.
Onsite CRM
Company
Nutshell
Organization
1:1Onsite CRM Company records map to Nutshell Organizations. We extract company name, address, domain, and any company-level custom fields from the CSV export. Organization is created before the People import so that the association lookup is satisfied at the moment of People insert. If the customer uses company-level tags or categories, these map to Nutshell Labels on the Organization record.
Onsite CRM
Deal
Nutshell
Deal
1:1Onsite CRM Deal records map to Nutshell Deals. The deal name, value, close date, and associated contact and company relationships migrate. Deal stage names from Onsite CRM's pipeline map to Nutshell pipeline stages during the stage mapping phase, with stage order and probability percentages preserved where Nutshell supports them. We extract deal owner information and resolve it against the User mapping.
Onsite CRM
Pipeline Stage
Nutshell
Pipeline Stage
lossyOnsite CRM's pipeline stages map to Nutshell pipeline stages. Each stage's name, position in the pipeline order, and win probability percentage transfer to Nutshell's stage definition. Nutshell Foundation is limited to one pipeline, so if the customer has multiple pipeline configurations in Onsite CRM, we consolidate to a single Nutshell pipeline and flag the mapping decision for customer review. Pro and Enterprise tiers support multiple pipelines.
Onsite CRM
Activity
Nutshell
Activity
1:1Onsite CRM activities including calls, SMS messages, and emails export from the UI. We map these to Nutshell Activity records attached to the relevant People or Organization. The activity type (call, email, note, meeting) maps to Nutshell's activity_type field, and the timestamp preserves the original activity date for timeline ordering. Activity content and notes transfer to the activity description field.
Onsite CRM
Task
Nutshell
Task
1:1Onsite CRM Task records migrate to Nutshell Tasks with assignee, due date, status, and description preserved. The task owner maps via email lookup against the Nutshell User records. If the task has a linked contact or deal in Onsite CRM, we resolve that association during the People and Deal import phase so the relationship is intact at Task import time.
Onsite CRM
Custom Field
Nutshell
Custom Field
lossyOnsite CRM custom fields vary by customer configuration and require manual field-by-field mapping during scoping. We flag each custom field on Contact, Company, Deal, and Activity objects for review, then create corresponding custom fields in Nutshell before migration. Nutshell's custom field limits are plan-dependent; Foundation has fewer custom fields than Pro or Enterprise. If the customer's custom field count exceeds the Nutshell plan limit, we identify the highest-priority fields for migration and flag the remainder for post-migration manual entry or plan upgrade.
Onsite CRM
User
Nutshell
User
1:1Onsite CRM User records (sales reps, admins) extract by email and name from the platform's user administration export. We resolve each user by email match against Nutshell User accounts. Any Onsite CRM user without a matching Nutshell account enters a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission structures in Onsite CRM do not transfer 1:1 because Nutshell's permission model is plan-dependent.
| Onsite CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | People1:1 | Fully supported | |
| Company | Organization1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline Stage | Pipeline Stagelossy | Fully supported | |
| Activity | Activity1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Custom Field | Custom Fieldlossy | Fully supported | |
| User | User1: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.
Onsite CRM gotchas
No public API documentation found
Weebly-hosted infrastructure limits data access
Limited historical activity export
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 audit
We audit the source Onsite CRM account via customer-supplied screenshots and in-app export previews to confirm what objects and fields the UI exposes. We document the custom field list, pipeline stage definitions, activity types, and user count. We pair this with a Nutshell plan review to confirm custom field limits and pipeline count against the customer's migration requirements. The scoping output is a written migration scope with field mapping for each object and a plan recommendation if custom field or pipeline constraints exist.
CSV export extraction and structuring
We guide the customer through generating CSV exports from Onsite CRM's in-app export interface for each object (Contacts, Companies, Deals, Activities, Tasks). Because Onsite CRM has no bulk API, exports are manual and bounded by UI export limits. We structure the raw CSV files, normalize field names, and identify any missing required fields for Nutshell import. We flag any records that exceed Onsite CRM's per-export limits for staged extraction.
Schema creation in Nutshell
We create the destination schema in the customer's Nutshell account before any data import. This includes creating any custom fields identified during scoping (confirmed against the Nutshell plan tier), setting up pipeline stages with order and probability mapping from Onsite CRM, and configuring labels for any tags or categories from Onsite CRM. If multiple Onsite CRM pipelines must consolidate into one Nutshell pipeline (Foundation tier), we document the consolidation mapping for customer review.
Test migration and reconciliation
We run a test migration using a subset of the exported data into the customer's Nutshell account. The customer reconciles record counts, spot-checks mapped fields against the source CSV, and validates that company-contact relationships and deal associations are intact. Any mapping corrections happen in the test phase before the full production migration runs. We do not proceed to production migration without customer sign-off on the test results.
Production migration in dependency order
We run the full production migration in dependency order: Organizations (from Companies), People (from Contacts with Organization lookup resolved), Deals (with contact and organization lookups resolved), Tasks, then Activities. Each phase emits a row-count reconciliation report. Owner mapping resolves Onsite CRM users to Nutshell User accounts by email match; any unresolved users enter the reconciliation queue for the customer's admin to provision.
Cutover, validation, and automation inventory handoff
We freeze Onsite CRM writes during cutover and run a final delta migration of any records modified during the migration window. We validate the final record counts in Nutshell against the source data. We deliver a written inventory of any Onsite CRM activity configurations, outbound sequences, or workflow-like setups requiring rebuild in Nutshell's automation tools. We support a brief post-migration window where we resolve any data quality issues raised by the customer's team.
Platform deep dives
Onsite CRM
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 Onsite CRM 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
Onsite CRM: Not publicly documented.
Data volume sensitivity
Onsite CRM 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 Onsite CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Onsite CRM 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 Onsite CRM
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.