CRM migration
Field-level mapping, validation, and rollback between PromoXcrm and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
PromoXcrm
Source
Nutshell
Destination
Compatibility
7 of 8
objects map 1:1 between PromoXcrm and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from PromoXcrm to Nutshell is a migration from a niche promotional-products CRM to a general SMB sales platform with a documented API, transparent per-user pricing, and a large established user base. PromoXcrm's industry-specific objects — Commission Records, Projects tied to promo orders, and internal Presentation files — have no direct Nutshell equivalents, so we export them as structured CSV records and provide the customer with a custom field creation guide to receive them in Nutshell. We sequence the migration to preserve the PromoXcrm pipeline stage history, resolve client-to-contact relationships, and handle attachment references tied to the promo order workflow. Workflow automations and task rules do not migrate; we deliver a written inventory of active rules for the customer's admin to rebuild in Nutshell. Nutshell's bulk import via CSV supports the migration pattern for standard objects, and the Nutshell API (documented at support.nutshell.com) handles engagement records and custom object writes.
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 PromoXcrm 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.
PromoXcrm
Leads
Nutshell
Lead
1:1PromoXcrm Lead records map directly to Nutshell Lead. We preserve lead source, pipeline stage, owner assignment, and any custom lead properties as Nutshell custom fields on the Lead object. Nutshell supports Text, Long Text, Currency, Date, Number, and Dropdown custom field types for Leads per support.nutshell.com. PromoXcrm industry-specific stage labels (Quote Sent, Artwork Approved, Order Confirmed) require manual creation as Nutshell Lead Status values or pipeline stage names during the custom field setup phase.
PromoXcrm
Clients
Nutshell
Person (Contact)
1:1PromoXcrm Client records represent the distributor's end customers and map to Nutshell Person. Standard fields (name, email, phone, company name) migrate directly. Any promo-specific custom properties on the Client record (client tier, referral source, preferred suppliers) require custom field creation in Nutshell's Person object before import. We extract these as separate columns in the migration CSV and document the field creation steps.
PromoXcrm
Pipeline
Nutshell
Pipeline (Nutshell)
lossyPromoXcrm's customizable pipelines with promo-specific stage names map to Nutshell Pipelines. Nutshell's Foundation tier supports one customizable pipeline; Pro ($42/user) and above support multiple pipelines. We extract the customer's current pipeline stages and probabilities during discovery and configure matching Nutshell pipeline stages before migration so that deal history maps to the correct stage values.
PromoXcrm
Projects
Nutshell
Custom Fields on Lead or Person
1:1PromoXcrm Projects represent individual promo orders or campaigns tied to a client. Projects have no direct Nutshell equivalent since Nutshell is a general CRM without a project management object. We export Project records with client association, dates, status, and product details as a structured CSV. The customer creates custom fields on Nutshell Lead or Person (e.g., last_project_name__c, last_project_date__c) to receive summary project data. Full project history requires a separate project tracking tool.
PromoXcrm
Commission Records
Nutshell
Custom Fields on Person
1:1Commission calculations are a PromoXcrm-specific feature for tracking rep or distributor commissions on promo orders. Commission records export as a structured CSV with fields for rep name, client, project, commission amount, and payout status. These map to custom fields on Nutshell Person (e.g., commission_earned__c, commission_paid__c). We cannot create a separate Commission object in Nutshell; the customer receives a migration CSV and a custom field creation guide for the Person object.
PromoXcrm
Tasks
Nutshell
Task
1:1PromoXcrm Task records migrate to Nutshell Task with assignees, due dates, status, and descriptions preserved. Nutshell Task objects support standard CRM task fields. Automated task-creation rules (if-this-then-that triggers tied to promo order stages) do not export; we document all active automation rules during the discovery call and provide a rebuild guide for Nutshell's workflow management feature. PromoXcrm's task automation scope typically adds a half-day to the migration timeline.
PromoXcrm
Presentations
Nutshell
File attachments on Person or Lead
1:1PromoXcrm Presentations are internal client-facing or internal sales assets stored within the CRM. We export available file references as a structured CSV with file names, associated client, project, and download URLs. Actual file hosting transfer depends on where PromoXcrm stores the files (internal storage or external link). We document the file inventory so the customer can re-upload to Google Drive, Dropbox, or Nutshell's file attachment mechanism post-migration.
PromoXcrm
Custom Objects
Nutshell
Custom Fields on Lead, Person, or Company
1:1PromoXcrm supports custom objects accessible via its web-service API. We query the custom object schema during discovery and export all accessible records. Since Nutshell does not support standalone custom object API names (only custom fields on standard objects), we decompose each PromoXcrm custom object into its constituent fields and map them to Nutshell custom fields on the appropriate standard object (Lead, Person, or Company). The customer receives a schema map showing which custom fields receive which PromoXcrm custom object data.
| PromoXcrm | Nutshell | Compatibility | |
|---|---|---|---|
| Leads | Lead1:1 | Mapping required | |
| Clients | Person (Contact)1:1 | Fully supported | |
| Pipeline | Pipeline (Nutshell)lossy | Fully supported | |
| Projects | Custom Fields on Lead or Person1:1 | Mapping required | |
| Commission Records | Custom Fields on Person1:1 | Mapping required | |
| Tasks | Task1:1 | Mapping required | |
| Presentations | File attachments on Person or Lead1:1 | Mapping required | |
| Custom Objects | Custom Fields on Lead, Person, or Company1:1 | Mapping required |
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.
PromoXcrm gotchas
No public API documentation or rate limit specification
Promo-specific objects have no direct equivalent in generic CRMs
Pricing inconsistency across sources may signal tier complexity
Workflow automations and task rules do not migrate
Vendor viability and support responsiveness are unverified
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 tier verification
We audit the PromoXcrm account to establish record counts (Leads, Clients, Projects, Tasks, Commission Records, Presentations), active integrations (Xero, Stripe, Mailchimp), and any custom object schemas accessible via the web-service API. We verify the customer's PromoXcrm active tier against the published pricing discrepancy ($45 flat vs $55/user with $449 setup) to confirm which features were in use. We request API credentials and conduct a direct API probe to establish safe extraction thresholds. If the API is undocumented or unreliable, we plan the CSV export fallback. The discovery output is a written migration scope with record counts per object and a Nutshell plan recommendation based on the customer's team size and pipeline complexity.
Nutshell custom field creation
Before any data import, we create the custom fields in Nutshell that will receive PromoXcrm's promo-specific data. Commission Records map to custom fields on Nutshell Person (e.g., commission_earned__c, commission_paid__c, commission_project__c). Project summary data maps to custom fields on Nutshell Person or Lead (e.g., last_project_name__c, last_project_date__c). Promo-specific stage labels from PromoXcrm pipelines map to Nutshell Lead Status or Pipeline Stage values. We provide a step-by-step field creation guide with field types (Text, Currency, Date, Dropdown) so the customer's Nutshell admin completes this configuration before the import phase begins.
PromoXcrm data extraction
We extract data from PromoXcrm using the API probe results or CSV export fallback. Extraction runs in batches to avoid overwhelming the source system and includes: Leads (with pipeline stage and owner), Clients/Persons (with all standard and custom fields), Projects (with client association, dates, status, product details), Commission Records (rep, client, project, amount, payout status), Tasks (assignee, due date, status, description), and Presentation file references (file name, client association, storage location). We run a pre-extraction data quality check to flag duplicate records, missing required fields, and inconsistent formats before transformation.
Data transformation and mapping
We transform the PromoXcrm export into Nutshell-compatible CSV files. Commission Records and Project summary data are decomposed into the custom field columns defined in step 2. Pipeline stage names are mapped to the Nutshell Pipeline stages configured in step 2. PromoXcrm client IDs are resolved to match the Nutshell Person records imported in step 5. Owner email addresses from PromoXcrm are mapped to Nutshell User accounts. We validate field formats (date formats, currency symbols, phone number structures) against Nutshell's expected input formats before import.
Nutshell import in dependency order
We import into Nutshell in record-dependency order: Persons first (standalone contact records), then Leads (with Person associations where applicable), then Tasks (linked to Person or Lead by email match). Commission and Project custom field data loads after the parent Person or Lead record exists to satisfy the field targets. Presentation file references are exported as a separate file inventory document for the customer to re-upload manually. Each phase emits a row-count reconciliation report. Nutshell's bulk import via CSV handles the standard objects; custom field writes use the Nutshell API or direct field mapping during the CSV import phase.
Cutover, validation, and automation handoff
We freeze PromoXcrm writes during cutover and run a final delta migration of any records modified during the migration window. We validate a random sample of 25-50 records against the PromoXcrm source to confirm field accuracy. We deliver the Workflow and Task Automation inventory document to the customer's Nutshell admin with rebuild recommendations for each active PromoXcrm rule. We support a three-day hypercare window to resolve reconciliation issues. We do not rebuild PromoXcrm workflows as Nutshell workflows inside the migration scope; that is a separate configuration task for the customer's admin.
Platform deep dives
PromoXcrm
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 PromoXcrm 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
PromoXcrm: Not publicly documented.
Data volume sensitivity
PromoXcrm 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 PromoXcrm to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your PromoXcrm 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 PromoXcrm
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.