CRM migration

Migrate from Onsite CRM to Nutshell

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

Onsite CRM logo

Onsite CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

6 of 8

objects map 1:1 between Onsite CRM and Nutshell.

Complexity

CModerate

Timeline

1-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Onsite CRM logo

Onsite CRM

What's pushing teams away

  • Extremely limited market presence with minimal third-party reviews and community discussion, making it difficult to assess long-term viability.
  • No publicly documented API, SDK, or webhook infrastructure limits integration options and blocks automated data extraction.
  • Appears to have weaker reporting and analytics depth compared to established CRM competitors like HubSpot or Pipedrive.
  • Very small user base on review platforms like G2 and Capterra suggests limited adoption and support ecosystem.
  • Lacks enterprise-grade features needed as teams scale, driving migration to platforms with better customization and API access.

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

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

maps to

Nutshell

People

1:1
Fully supported

Onsite 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

maps to

Nutshell

Organization

1:1
Fully supported

Onsite 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

maps to

Nutshell

Deal

1:1
Fully supported

Onsite 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

maps to

Nutshell

Pipeline Stage

lossy
Fully supported

Onsite 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

maps to

Nutshell

Activity

1:1
Fully supported

Onsite 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

maps to

Nutshell

Task

1:1
Fully supported

Onsite 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

maps to

Nutshell

Custom Field

lossy
Fully supported

Onsite 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

maps to

Nutshell

User

1:1
Fully supported

Onsite 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.

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.

Onsite CRM logo

Onsite CRM gotchas

High

No public API documentation found

Medium

Weebly-hosted infrastructure limits data access

Medium

Limited historical activity export

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 API means CSV-only extraction with UI constraints

    Onsite CRM has no documented REST API, SDK, or webhook system according to apitracker.io, meaning all data extraction relies entirely on in-app CSV exports. If the customer has more than 10,000 records or complex custom field configurations, export size limits in the Weebly-hosted UI become a bottleneck we flag during scoping. We request customer-supplied screenshots of their data structure during scoping to confirm what objects and fields the UI actually exposes before designing the migration sequence.

  • Custom field count may exceed Nutshell plan limits

    Onsite CRM custom field structures vary by customer configuration, and Nutshell's custom field limits are plan-dependent. Foundation has more restrictive limits than Pro or Enterprise. If the customer's Onsite CRM instance uses a large number of custom fields, migration may require a Nutshell plan upgrade or a prioritization exercise to identify which fields are highest-value for migration. We identify this constraint during scoping and flag it before migration begins.

  • Limited historical activity export in single CSV download

    CRM migration reviews consistently surface that teams want multi-year activity history (call notes, email logs, SMS threads). Onsite CRM's in-app export options may not include rich activity history in a single downloadable file. We advise customers to request a pre-migration export of activity records separately and budget time for any manual activity re-entry post-migration if the export is incomplete. Activity records are migrated as a distinct phase after the core Contact, Company, and Deal migration.

  • Pipeline consolidation required on Nutshell Foundation

    Nutshell Foundation is limited to a single pipeline. If the customer uses multiple deal pipelines in Onsite CRM, we consolidate them into one Nutshell pipeline during migration and document the stage mapping for each original pipeline. Pro, Power AI, and Enterprise tiers support multiple pipelines, so customers who need to preserve separate pipeline configurations should confirm their Nutshell plan during scoping.

Migration approach

Six steps for a successful Onsite CRM to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Onsite CRM logo

Onsite CRM

Source

Strengths

  • Combines CRM, calling, SMS, and email marketing in a single subscription for small teams.
  • Weebly-hosted platform offers straightforward initial setup for businesses already using Weebly.
  • Provides basic pipeline visualization and deal tracking for straightforward sales processes.
  • Lead conversion tools and real-time outreach automation for teams prioritizing outbound activity.
  • Established in 2010, indicating over a decade of operational history.

Weaknesses

  • No publicly documented REST API, SDK, or webhook system according to apitracker.io, severely limiting programmatic integrations and data extraction options.
  • Extremely limited market visibility with minimal reviews, community discussion, or third-party integrations.
  • Appears to lack enterprise-grade features like advanced reporting, custom objects, or sophisticated workflow automation.
  • Data export is limited to in-app CSV/PDF options with no bulk API access, complicating large-scale migrations.
  • Small user base and limited review presence make it difficult to assess platform reliability and long-term vendor viability.
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 Onsite CRM 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

    Onsite CRM: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most migrations complete in one to three weeks for straightforward accounts under 5,000 Contacts and 1,000 Deals with no complex custom field configurations. Migrations with multiple years of activity history, large custom field sets, or customers needing pipeline consolidation on a Foundation plan move to four to eight weeks because of manual CSV structuring and reconciliation testing. The extraction phase (generating CSV exports from Onsite CRM) is customer-paced and can extend the timeline if the account has large data volumes requiring staged exports.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Onsite CRM.
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