CRM migration

Migrate from PBS Systems to Nutshell

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

PBS Systems logo

PBS Systems

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between PBS Systems and Nutshell.

Complexity

BStandard

Timeline

72–96 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

PBS Systems v10 APEX is a full-stack dealer management system built around automotive workflows: vehicle inventory, F&I product deals, service write-ups, parts ordering, and integrated accounting. Nutshell CRM is a lightweight sales-focused platform built around People, Companies, Leads, Deals, and Activities. These platforms share almost no object-level vocabulary, so migration requires deliberate deconstruction of PBS's automotive domain model and reconstruction within Nutshell's general CRM schema. We extract PBS customer records, vehicle associations, F&I deals, and service history via the PBS export interface, then map those into Nutshell's People and Companies with custom fields for automotive context. PBS's vehicle stock numbers, VINs, and deal structures become Nutshell custom fields on Deals. Service records that require granular tracking migrate as Nutshell Activities with custom field payloads for repair order numbers, RO status, and labor codes. What does not migrate: PBS fixed-ops workflows, service dispatch rules, parts reorder triggers, and RouteOne credit integration require Nutshell-native rebuilds. Accounting modules (GL, AP, AR) do not have a Nutshell equivalent — that data stays in PBS or moves to separate accounting software. FlitStack AI sequences the migration so foreign-key dependencies resolve correctly: Companies first, then People with company links, then Deals with linked People and custom automotive fields, then Activities. A delta-pickup window captures any records modified during the cutover window.

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

PBS Systems logo

PBS Systems

What's pushing teams away

  • Fixed-operations workflow at point of sale is time-consuming and keyboard-light, requiring excessive mouse navigation compared to ADP/CDK.
  • Service write-up and parts counter operations run measurably slower than competing DMS platforms, creating bottlenecks during high-volume periods.
  • Shipping and receiving workflows take 3-4 times longer than ADP/CDK, causing dealerships to fall behind on returns and freight processing.
  • Latest v10 APEX UI update consolidated window separations that staff relied on, making previously accessible functions harder to locate.
  • Slow program loading and delayed clock-in recording frustrate staff who use the system daily, particularly on older hardware.

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 PBS Systems objects map to Nutshell

Each row shows how a PBS Systems 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.

PBS Systems

Customer (Contact)

maps to

Nutshell

Person

1:1
Fully supported

PBS customer records map directly to Nutshell People. The primary contact fields (name, phone, email, address) transfer 1:1. PBS customer records without email receive a placeholder email flag so the Nutshell admin can complete the record manually before the full migration.

PBS Systems

Dealership Company

maps to

Nutshell

Company

1:1
Fully supported

PBS stores the dealership entity as an internal company record. This maps to a Nutshell Company record. If the PBS instance contains multiple franchise locations, each location becomes a separate Nutshell Company so pipeline ownership can be assigned per location.

PBS Systems

Vehicle (Inventory Unit)

maps to

Nutshell

Custom fields on Deal

1:1
Fully supported

PBS vehicle inventory records carry VIN, stock number, year/make/model, mileage, and trim — none of which have Nutshell native equivalents. We extract these as custom fields (Vehicle_VIN__c, Stock_Number__c, Year_Make_Model__c, Mileage__c) and attach them to the associated Nutshell Deal that represents the F&I transaction.

PBS Systems

F&I Deal / Deal Jacket

maps to

Nutshell

Deal

1:1
Fully supported

PBS F&I deals are the core transaction record: vehicle, customer, finance products, rates, term, and payment. Nutshell Deals capture the commercial terms but not the full F&I product structure. We map the deal value, stage, and close date; F&I product selections (GAP, tire protection, service contract) store as custom fields on the Nutshell Deal record.

PBS Systems

Trade-In Vehicle

maps to

Nutshell

Custom fields on Deal

1:1
Fully supported

PBS trade-in records capture the trade vehicle VIN, year/make/model, mileage, and appraisal value. These attributes map to Nutshell Deal custom fields: Trade_VIN__c, Trade_Mileage__c, and Trade_Appraisal_Value__c. Trade equity or negative equity amounts are preserved as signed currency fields to maintain continuity for F&I desk review and ensure accurate deal structuring in Nutshell.

PBS Systems

Service Appointment / Work Order

maps to

Nutshell

Activity (Task)

1:1
Fully supported

PBS service write-ups and appointments are not Opportunities — they are operational records. We migrate them as Nutshell Activities (Tasks) with custom fields for RO number, service advisor, labor codes, and status. Historical service records older than 24 months can be archived as read-only activities at the customer's Nutshell profile.

PBS Systems

Parts Order / PO

maps to

Nutshell

Activity (Task)

1:1
Fully supported

Parts orders map to Nutshell Activities with custom fields capturing the PO number, parts total amount, and vendor information. This approach preserves the complete parts purchasing history at the customer level without requiring a full parts-inventory management system within Nutshell, maintaining context for service history and parts sourcing analysis.

PBS Systems

Sales Lead (unsold prospect)

maps to

Nutshell

Lead

1:1
Fully supported

PBS leads representing showroom traffic that did not result in a sale (unsold prospects) migrate as Nutshell Leads. Source attribution fields such as how the prospect heard about the dealership or which marketing campaign referred them transfer as custom fields if that data exists in PBS, preserving marketing attribution for follow-up and analysis.

PBS Systems

RouteOne Credit Application

maps to

Nutshell

Deal custom fields

1:1
Fully supported

RouteOne credit application records link to F&I deals in PBS. The credit application outcome (approved/denied/conditioned), lender name, and term submitted migrate as custom fields on the Nutshell Deal. RouteOne itself does not transfer — that integration must be rebuilt in Nutshell if required.

PBS Systems

Account / GL Entry

maps to

Nutshell

No equivalent in Nutshell

1:1
Fully supported

PBS accounting modules (GL, AP, AR, cash control) have no Nutshell equivalent. These records do not migrate. Dealerships should move accounting to a dedicated platform (QuickBooks, CDK Financial Suite, or similar) or retain PBS for accounting only while migrating sales CRM to Nutshell.

PBS Systems

User / Employee

maps to

Nutshell

User (via email match)

1:1
Fully supported

PBS employee records map to Nutshell users by matching email addresses between systems. Employees with no email address in PBS cannot be auto-matched and are flagged for manual review before migration so the Nutshell admin can create user accounts and assign their records to a fallback owner to preserve data continuity.

PBS Systems

Attachment / Document

maps to

Nutshell

Activity attachments

1:1
Fully supported

PDFs, images, and documents attached to PBS deals and service records are extracted and reattached to the corresponding Nutshell Activities and Deals. File size limits are respected; documents exceeding 25MB are flagged for manual delivery to prevent transfer issues and preserve critical attachments during the migration process.

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.

PBS Systems logo

PBS Systems gotchas

High

No public data export API for self-serve migration

Medium

Custom fields vary per dealership with no standard schema

Medium

Service history links to parts and technicians require careful relationship mapping

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

  • PBS F&I product bundles must be decomposed into individual custom fields

    PBS F&I deals store product selections (GAP, tire protection, service contract, dent removal, prepaid maintenance) as a bundled deal record with product codes and pricing. Nutshell Deals have no native F&I product fields — each product must be mapped to a custom boolean or currency field on the Deal. If PBS uses product bundles with internal codes that do not map to human-readable names, the migration plan must include a reference table for each product code so custom field labels are accurate. We deliver this reference table before migration so Nutshell admins can validate field labels before data lands.

  • RouteOne credit application data has no Nutshell equivalent and does not transfer

    PBS integrates with RouteOne for credit application submission, financing verification, and compliance documentation. Nutshell has no native integration with RouteOne and no equivalent credit application object. Credit application records (applicant SSN, lender response codes, deal structure from RouteOne) cannot be stored in Nutshell's standard schema. We extract the credit application outcome, lender name, and approval status as custom Deal fields, but the full compliance documentation stays in PBS or RouteOne. The dealership must evaluate whether to maintain a RouteOne login separately or rebuild the credit workflow within Nutshell using available integrations.

  • PBS service history volume can exceed Nutshell's activity capacity for high-volume dealers

    Large dealerships generate hundreds of service write-ups per month over multi-year periods. Migrating every historical RO as a separate Nutshell Activity can create thousands of activity records on individual customer profiles, which degrades Nutshell list-view performance and makes activity history difficult to scan. We recommend migrating the most recent 24 months of service history as full Activity records and archiving older records as a single historical summary note on the customer profile. This is configurable — the dealership chooses the cutoff date before migration runs.

  • PBS multi-dealership instances require dealership-level segmentation in Nutshell

    Many PBS deployments cover multiple franchise locations under a single database. Nutshell does not have a native multi-org model — each Nutshell account is a single company. If the migration covers multiple dealerships, FlitStack creates separate Nutshell accounts per location and assigns pipeline ownership at the account level. Alternatively, a single Nutshell account can use Team features to segment records by location, but this requires pre-migration setup of Nutshell Teams and access rules. We deliver a segmentation plan before migration so each dealership's data lands in the correct Nutshell context.

  • PBS fixed-ops workflows and automation rules do not migrate and cannot be translated

    PBS service dispatch rules, parts reorder triggers, and F&I workflow automations are built on PBS's internal process engine. Nutshell's automation is limited to task creation triggers and email sequences — it has no equivalent to PBS's service dispatch or parts replenishment logic. Any automated process that routes service vehicles, triggers parts orders based on service completion, or generates F&I product recommendations must be rebuilt in Nutshell manually or through a Nutshell-supported integration. We export PBS workflow definitions as a reference document so the Nutshell admin can evaluate which processes are critical to rebuild.

Migration approach

Six steps for a successful PBS Systems to Nutshell data migration

  1. Extract PBS data via Database Export Interface

    We connect to your PBS instance using the Database Export Interface (DEI) to extract customer records, vehicle inventory, F&I deals, service history, and parts orders. The DEI outputs structured data in a format we can parse for transformation. We run a pre-migration audit to identify record counts, custom field definitions, and any data quality issues (duplicate records, missing email addresses, invalid VINs) before mapping begins. This audit generates a data quality report that both teams review before the migration plan is finalized.

  2. Build the PBS-to-Nutshell mapping plan and reference tables

    We build the full mapping specification: People fields, Company fields, Deal fields, Activity fields, and every custom field needed for automotive context. F&I product codes are translated to human-readable labels using a reference table provided by your team or derived from PBS configuration. Dealership segmentation for multi-location PBS instances is defined at this stage. The mapping plan is reviewed and approved before any migration runs.

  3. Run sample migration with field-level diff

    A representative sample — typically 200–500 records spanning customers, vehicles, deals, and service history — migrates to Nutshell first. We generate a field-level diff showing source values vs. destination values so you can verify VIN accuracy, deal value preservation, F&I product field labels, and owner assignment. You review the sample in Nutshell and request any mapping adjustments before the full run commits.

  4. Execute full migration with delta-pickup window

    Full migration runs against Nutshell's JSON-RPC API. We sequence object types so foreign-key dependencies resolve correctly: Companies first, then People with company links, then Deals with linked People and custom automotive fields, then Activities. A delta-pickup window (24–48 hours) captures records modified in PBS during the cutover so Nutshell reflects PBS's final state at go-live. All operations are logged in an audit trail; one-click rollback is available if reconciliation fails.

Platform deep dives

Context on both ends of the pair

PBS Systems logo

PBS Systems

Source

Strengths

  • Unified single-database architecture connects all dealership departments without data silos between Sales, Service, Parts, and Accounting.
  • Active product development with demonstrated responsiveness to dealer feedback and feature requests.
  • Comprehensive training resources through PBS Academy support staff onboarding and ongoing education.
  • Live phone support with actual people rather than automated bots, available across North American time zones.

Weaknesses

  • Fixed-operations workflows (service write-up, parts counter) are documented as slower than ADP/CDK equivalents, impacting advisor efficiency metrics.
  • Limited public API documentation makes programmatic data extraction non-standard and requires bespoke tooling for migration.
  • Data export and migration tooling is not publicly documented, making self-serve data extraction difficult without vendor coordination.
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?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across PBS Systems and Nutshell.

  • Object compatibility

    B

    2 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

    PBS Systems: Not publicly documented..

  • Data volume sensitivity

    B

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

Estimator

Estimate your PBS Systems 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 PBS Systems to Nutshell data migrations

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

Can't find your answer?

Walk through your PBS Systems to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most PBS to Nutshell migrations complete in 72–96 hours of clock time for under 50,000 records. Large multi-franchise dealerships with 100,000+ records and complex F&I product structures extend to 5–10 business days. The longest phase is building the automotive custom field schema in Nutshell before data can land — pre-migration setup of Vehicle, Trade, and F&I product fields typically takes 2–3 days of coordination with your Nutshell admin.

Adjacent paths

Related migrations to explore

Ready when you are

Move from PBS Systems.
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