CRM migration
Field-level mapping, validation, and rollback between Pepper Cloud and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Pepper Cloud
Source
Nutshell
Destination
Compatibility
8 of 9
objects map 1:1 between Pepper Cloud and Nutshell.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Pepper Cloud to Nutshell is a schema-normalizing migration. Pepper Cloud maintains Leads, Contacts, and Accounts as three separate objects; Nutshell consolidates Prospects into People (with a lead status field) and Organizations into Companies. We resolve that structure difference at scoping by classifying every Pepper Cloud Contact as either a Nutshell Person with lead status active or a Person linked to a Company, then use the Company as the dedupe anchor for all Person records. Pipeline stage names, deal amounts, close dates, and owner assignments migrate directly. We flag WhatsApp message content as non-exportable from Pepper Cloud's private API and advise customers to export chat history separately if message context is business-critical. Custom fields require type compatibility checks against Nutshell's supported field types, and workflow automation rules do not migrate as code — we deliver a written inventory for the customer to rebuild.
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 Pepper Cloud 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.
Pepper Cloud
Contact
Nutshell
Person
1:1Pepper Cloud Contacts map directly to Nutshell Person records. Standard fields (name, email, phone, address) migrate 1:1. If the Pepper Cloud Contact has an associated Account, we link the Person to the corresponding Nutshell Company via the personId lookup. Pepper Cloud's contact type or lifecycle designation migrates into Nutshell's personStatus field on the Person record for segmentation.
Pepper Cloud
Lead
Nutshell
Person (lead status)
1:1Pepper Cloud Leads map to Nutshell Person records with the personStatus field set to active or lead. Lead source attribution (web form, WhatsApp, Facebook, Instagram, Telegram) migrates to a custom text field or tag in Nutshell. We preserve the original lead score or priority rating in a custom field so the sales team can re-prioritize leads after cutover.
Pepper Cloud
Account
Nutshell
Company
1:1Pepper Cloud Accounts map to Nutshell Company records with company name, website, address, and industry fields preserved. Parent-child hierarchy (if configured in Pepper Cloud) maps to Nutshell's nested company structure or a custom lookup field. Company records are created before any Person import to satisfy the Person-to-Company lookup.
Pepper Cloud
Opportunity
Nutshell
Deal
1:1Pepper Cloud Opportunities map to Nutshell Deals with amount, close date, owner, and stage name preserved. The pipeline association in Pepper Cloud maps to the Nutshell pipeline assignment. Stage names vary by Pepper Cloud workspace, so we explicitly map each stage to the nearest Nutshell stage or create matching custom stages in the destination before migration.
Pepper Cloud
Pipeline Stages
Nutshell
Deal Stages
lossyEach Pepper Cloud pipeline becomes a Nutshell pipeline. Stage names migrate verbatim; stage probability percentages map to Nutshell's stage configuration. If Nutshell's default stages do not match the Pepper Cloud taxonomy, we create custom stages in the destination pipeline before Deal migration begins.
Pepper Cloud
User / Owner
Nutshell
User
1:1Pepper Cloud Users (owner field on records) map to Nutshell Users by email match. We extract all distinct owners from Contacts, Leads, Accounts, and Opportunities and reconcile against the Nutshell User list. Any Owner without a matching Nutshell User is held in a reconciliation queue for the customer to provision before record import resumes.
Pepper Cloud
Custom Fields
Nutshell
Custom Fields
1:1Pepper Cloud custom fields on Contacts, Leads, Accounts, and Opportunities require type compatibility check against Nutshell's supported custom field types (Text 225 chars max, Long Text, Currency, Date, and select dropdown options). Checkbox fields from Pepper Cloud map to Nutshell dropdowns (Yes/No). Long-text fields truncated to Nutshell's display limits are flagged for customer review. Custom field schemas are audited before migration to avoid silent type-mismatch failures.
Pepper Cloud
Task
Nutshell
Task
1:1Pepper Cloud Tasks linked to Contacts, Leads, or Opportunities migrate to Nutshell Tasks with due date, assignee, status, and description preserved. Task assignment resolves the Pepper Cloud owner to the corresponding Nutshell User by email. Recurring task frequency migrates as a text note if Nutshell's task model does not support recurrence natively on Starter plans.
Pepper Cloud
Tag / Label
Nutshell
Tag
1:1Tags applied to Pepper Cloud Contacts, Leads, and Opportunities migrate as flat label strings in Nutshell's tag field. Nutshell uses a simple tagging model without hierarchy, so any hierarchical or nested tag structures in Pepper Cloud are flattened into pipe-delimited tag strings for migration.
| Pepper Cloud | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Lead | Person (lead status)1:1 | Fully supported | |
| Account | Company1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Pipeline Stages | Deal Stageslossy | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Custom Fields | Custom Fields1:1 | Mapping required | |
| Task | Task1:1 | Fully supported | |
| Tag / Label | Tag1: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.
Pepper Cloud gotchas
WhatsApp conversation content cannot be exported via API
Custom field schema varies by pricing tier
Pricing is quote-only with no public rate card
No public bulk export or documented API rate limits
Workflow automation rules are not portable
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 scoping call
We audit the source Pepper Cloud workspace for user count, plan tier (Starter, Business, Enterprise), record volumes across Contacts, Leads, Accounts, Opportunities, Tasks, and custom fields. We verify the plan tier because custom field availability, record limits, and API access scope are tier-gated. We extract the pipeline stage inventory and workflow rule list. This phase produces a written migration scope with record counts per object, a list of custom fields requiring type translation, and a preliminary pipeline mapping.
Schema audit and field type compatibility check
We audit every Pepper Cloud custom field against Nutshell's supported custom field types. Checkbox fields, multi-select fields, and fields exceeding Nutshell's 225-character Text limit are flagged with a proposed translation strategy. We identify any Pepper Cloud custom object usage and report it as a gap against Nutshell's feature set. This audit is shared with the customer before any data extraction begins so that the field translation approach is agreed upon.
Sample migration and mapping validation
We run a sample extraction of up to 100 random records from Pepper Cloud across Contacts, Leads, Accounts, and Opportunities and load them into a Nutshell staging environment. The customer reviews the mapped records and confirms field alignment, pipeline stage mapping, and owner assignment. We correct any mapping errors identified during the sample review before proceeding to full migration.
Owner reconciliation and User provisioning
We extract every distinct Pepper Cloud User referenced as an owner on Contacts, Leads, Accounts, Opportunities, and Tasks and match by email against the Nutshell destination User list. Owners without a matching Nutshell User are held in a reconciliation queue. The customer provisions any missing Users in Nutshell and confirms active or inactive status before record import resumes. This step is required because Nutshell's ownerId reference must be satisfied at the time of record insert.
Full migration in dependency order
We run production migration in record-dependency order: Companies (from Pepper Cloud Accounts) first, then People (Contacts and Leads with the personStatus distinction), then Deals (Opportunities with pipeline and stage resolved), then Tasks and tags. Custom field values are transformed during extraction to match Nutshell's type constraints. Each phase emits a row-count reconciliation report showing source count, migrated count, and error count before the next phase begins.
Cutover, delta sync, and automation inventory handoff
We freeze Pepper Cloud writes during cutover, run a delta migration of any records modified during the migration window, then confirm Nutshell as the system of record. We deliver the Workflow Automation Inventory document listing every Pepper Cloud workflow rule with its trigger conditions, actions, and recommended Nutshell Autoplay equivalent. We support a one-week post-cutover window to resolve any reconciliation issues. Workflow rebuild in Nutshell is outside standard scope and is handed to the customer's admin team.
Platform deep dives
Pepper Cloud
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 Pepper Cloud 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
Pepper Cloud: Not publicly documented.
Data volume sensitivity
Pepper Cloud 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 Pepper Cloud to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Pepper Cloud 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 Pepper Cloud
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.
