CRM migration
Field-level mapping, validation, and rollback between PBS Systems and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
PBS Systems
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between PBS Systems and Nutshell.
Complexity
BStandard
Timeline
72–96 hours
Overview
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.
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 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)
Nutshell
Person
1:1PBS 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
Nutshell
Company
1:1PBS 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)
Nutshell
Custom fields on Deal
1:1PBS 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
Nutshell
Deal
1:1PBS 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
Nutshell
Custom fields on Deal
1:1PBS 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
Nutshell
Activity (Task)
1:1PBS 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
Nutshell
Activity (Task)
1:1Parts 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)
Nutshell
Lead
1:1PBS 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
Nutshell
Deal custom fields
1:1RouteOne 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
Nutshell
No equivalent in Nutshell
1:1PBS 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
Nutshell
User (via email match)
1:1PBS 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
Nutshell
Activity attachments
1:1PDFs, 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.
| PBS Systems | Nutshell | Compatibility | |
|---|---|---|---|
| Customer (Contact) | Person1:1 | Fully supported | |
| Dealership Company | Company1:1 | Fully supported | |
| Vehicle (Inventory Unit) | Custom fields on Deal1:1 | Fully supported | |
| F&I Deal / Deal Jacket | Deal1:1 | Fully supported | |
| Trade-In Vehicle | Custom fields on Deal1:1 | Fully supported | |
| Service Appointment / Work Order | Activity (Task)1:1 | Fully supported | |
| Parts Order / PO | Activity (Task)1:1 | Fully supported | |
| Sales Lead (unsold prospect) | Lead1:1 | Fully supported | |
| RouteOne Credit Application | Deal custom fields1:1 | Fully supported | |
| Account / GL Entry | No equivalent in Nutshell1:1 | Fully supported | |
| User / Employee | User (via email match)1:1 | Fully supported | |
| Attachment / Document | Activity attachments1: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.
PBS Systems gotchas
No public data export API for self-serve migration
Custom fields vary per dealership with no standard schema
Service history links to parts and technicians require careful relationship mapping
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
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.
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.
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.
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
PBS Systems
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 PBS Systems 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
PBS Systems: Not publicly documented..
Data volume sensitivity
PBS Systems 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 PBS Systems to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave PBS Systems
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.