How long does a PBS Systems to Salesforce Sales Cloud migration take?

Most PBS-to-Salesforce migrations complete within 48–72 hours for dealerships with fewer than 50,000 customer and vehicle records. Larger dealerships with 200,000+ records, multiple F&I product types, and active service histories extend to 5–10 days. The longest single step is pre-creating Record Types and custom fields in Salesforce before the sample migration runs — typically 3–5 business days depending on admin availability. Timeline is measured from the day the PBS export file is delivered to FlitStack.

Will my PBS workflows and automation rules migrate to Salesforce Flow?

No. PBS workflows, approval rules, and automation sequences are DMS-native logic that do not transfer to Salesforce. Salesforce Flow handles automation differently — triggers, decisions, and actions are rebuilt from scratch using the PBS workflow export as a reference document. We provide a written workflow inventory derived from your PBS configuration that your Salesforce admin or implementation partner can use to rebuild automations in Flow or Process Builder after data migration completes.

What does a PBS Vehicle Deal become in Salesforce?

Each PBS Vehicle Deal maps to a Salesforce Opportunity with a pre-assigned RecordTypeId based on deal_type (New Vehicle, Used Vehicle, or Fleet). Deal amount, close date, stage, and owner map directly. F&I product selections become OpportunityLineItems linked to the Opportunity, each referencing a Product2 record. The vehicle VIN is stored in Vehicle_VIN__c on the Opportunity for reference back to the Asset record. Trade-in VIN and lender name migrate as custom fields.

Can I migrate PBS custom fields to Salesforce custom fields?

Yes. PBS custom fields are extracted during the export and included in the migration plan as a custom field creation checklist. Each PBS custom field is created in Salesforce with the matching field type and, for pick-list fields, the exact same pick-list values. Fields are created before the sample migration runs. We do not automatically create fields in your Salesforce org — the checklist is delivered to your admin for manual creation, then we validate the setup before proceeding.

What happens to PBS service write-up records in Salesforce?

PBS Repair Order records become Salesforce Case records linked to the serviced Asset (vehicle) and the customer Contact. The RO number is stored in RO_Number__c (custom field) since Salesforce auto-generates Case.CaseNumber. Labor hours and parts totals migrate as custom currency and number fields (Labor_Hours__c, Parts_Total__c). Advisor notes become the Case Description. Original service date is preserved in Original_Service_Date__c for historical reporting.

Does the migration affect my PBS account during cutover?

No. FlitStack AI uses scoped read access on PBS — your team continues operating in PBS throughout the migration. A delta-pickup window of 24–48 hours after the full migration runs captures any records created or modified in PBS during the cutover period. Your PBS data is never altered by the migration process, and the delta window ensures Salesforce reflects the final state of PBS at go-live.

How do I handle PBS parts inventory in Salesforce?

PBS parts inventory maps to Salesforce Product2 records with the part number as ProductCode and list price as StandardPrice. For parts bin locations and lot tracking, a custom object (Parts_Location__c) with lookups to Product2 and Account is recommended — your admin configures this post-migration. Salesforce's standard inventory model is not designed for DMS-style parts bin tracking, so the custom object approach provides the closest functional equivalent within the Salesforce platform.

What staff and user mapping is required before migration runs?

PBS staff records are matched to Salesforce Users by email address. Your admin must ensure that all PBS staff who should be Salesforce users have an active User record in Salesforce with a matching email before migration. Unmatched PBS owners are flagged in a pre-migration report with their email and role. The admin either creates Salesforce Users for them or assigns a fallback owner in the migration settings. Profile and Role assignments for each PBS role are documented in a staff mapping worksheet delivered during planning.

PBS Systems to Salesforce Sales Cloud Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

PBS Systems v10 APEX stores dealership data in a unified single-database structure covering sales, service, parts, and accounting modules. The CRM layer holds customer records linked to vehicle purchase histories, F&I products, and service write-ups — but PBS has no native Lead/Contact split and no opportunity pipeline model. Salesforce Sales Cloud separates Leads from Contacts, uses Account as the primary company object, Opportunity with StageName and RecordTypeId for deals, and Asset for vehicle records. We extract PBS customer records and vehicle deals via the PBS export interface, resolve PBS owner email addresses against Salesforce users, then migrate Customers to Contact (or Lead based on status), Companies to Account, Vehicle Deals to Opportunity with custom vehicle fields, and Service Records to Case. Workflows, automation rules, and DMS-specific configurations (parts pricing rules, F&I product logic) cannot migrate and must be rebuilt in Salesforce or third-party tools. Data validation runs against field-level requirements before commit to ensure referential integrity across migrated records.

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.

Object mapping

How PBS Systems objects map to Salesforce Sales Cloud

Each row shows how a PBS Systems object lands in Salesforce Sales Cloud, 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

maps to

Salesforce Sales Cloud

Contact

1:1

Fully supported

PBS Customer records map directly to Salesforce Contact. Each Contact requires an AccountId — PBS customers without a linked Company record attach to a default Unassigned Account. The PBS customer status field (Prospect, Active, Inactive) determines whether the record lands as a Contact or routes to Lead in Salesforce.

PBS Systems

Customer (status = Prospect)

maps to

Salesforce Sales Cloud

Lead

1:many

Fully supported

PBS Customer records where status = Prospect route to Salesforce Lead. The Lead.Status pick-list maps from PBS customer status values. PBS Customer records where status = Active, Sold, or Service-Only land as Salesforce Contacts. The split logic runs during migration based on the source status value.

PBS Systems

Company/Dealer Account

maps to

Salesforce Sales Cloud

Account

1:1

Fully supported

PBS Company records (the dealer franchise entity itself, not individual customers) map to Salesforce Account. Multi-location dealers using PBS sub-company structures map to Account hierarchies via the ParentId field. PBS company-level custom properties become custom fields on Account with __c suffix.

PBS Systems

Vehicle Deal

maps to

Salesforce Sales Cloud

Opportunity

1:1

Fully supported

PBS Vehicle Deals contain deal data (sale price, F&I products, trade-in, lender terms) linked to a customer and a vehicle inventory record. These map to Salesforce Opportunity with custom fields capturing F&I product selections, trade-in VIN, and lender name. The Opportunity.StageName maps from PBS deal stage values via value-by-value mapping. RecordTypeId requires pre-creation in Salesforce for each deal type (New Vehicle, Used Vehicle, Fleet).

PBS Systems

Vehicle Inventory

maps to

Salesforce Sales Cloud

Asset

1:1

Fully supported

PBS vehicle inventory records (stock units with VIN, trim, color, lot location) map to Salesforce Asset. VIN maps to Asset.SerialNumber, vehicle make/model maps to custom fields (Make__c, Model__c, Trim__c, Lot_Status__c). Active inventory assets link to the dealer Account via AccountId; sold vehicles link to the customer Contact via ContactId.

PBS Systems

Service Record / Repair Order

maps to

Salesforce Sales Cloud

Case

1:1

Fully supported

PBS service write-up records (RO number, labor lines, parts lines, technician, advisor notes, service date) map to Salesforce Case. Custom fields capture RO_Number__c, Labor_Lines__c, Parts_Lines__c, and Technician__c. Case.AccountId links to the Asset or Contact representing the serviced vehicle. Original service dates migrate as custom datetime fields for reporting continuity.

PBS Systems

F&I Product

maps to

Salesforce Sales Cloud

Opportunity Line Item

many:1

Fully supported

PBS F&I product selections (GAP, paint protection, extended warranty, tire-and-wheel) attached to a Vehicle Deal merge into Salesforce OpportunityLineItems on the corresponding Opportunity. Each F&I product becomes a line item with Quantity=1 and UnitPrice=product price. Product2 records must pre-exist in Salesforce or be created during migration.

PBS Systems

Parts Inventory

maps to

Salesforce Sales Cloud

Product2

1:1

Mapping required

PBS parts inventory records map to Salesforce Product2. Part number maps to ProductCode, description maps to Description, list price maps to StandardPrice. For parts-only queries Salesforce Product2 is sufficient; for bin-location tracking a custom object (Parts_Location__c) with lookups to Product2 is recommended.

PBS Systems

Staff / User

maps to

Salesforce Sales Cloud

User

1:1

Fully supported

PBS staff records resolve by email address to existing Salesforce User records. Unmatched PBS staff are flagged for manual User creation before the migration runs. PBS role and department fields can be mapped to Salesforce Profile and Role hierarchy in a supplemental mapping document.

PBS Systems

Note / Document Attachment

maps to

Salesforce Sales Cloud

ContentDocument / Note

1:1

Fully supported

PBS document attachments and notes linked to customer or vehicle records migrate as Salesforce Files (ContentDocument) for Lightning Experience compatibility. File size limits of 25MB per Salesforce File apply. Inline images in notes are downloaded and rehosted as Salesforce Files.

PBS Systems

Custom Field (PBS user-defined)

maps to

Salesforce Sales Cloud

Custom Field (__c)

1:1

Fully supported

PBS custom fields on any object require pre-creation in Salesforce as custom fields with the __c suffix. The migration plan delivered before migration runs includes a custom-field creation checklist with field type, pick-list values, and help text for each custom field. Fields are created before the sample migration runs.

PBS Systems

PBS Workflow / Automation

maps to

Salesforce Sales Cloud

Salesforce Flow

1:1

Fully supported

PBS workflows, approval rules, and automation sequences have no direct Salesforce equivalent. FlitStack exports PBS workflow definitions as a written reference document for the customer's Salesforce admin or implementation partner to rebuild using Flow. Automations are not migrated automatically. Customers use this document to manually reconstruct automation logic in Salesforce Flow.

PBS Systems	Salesforce Sales Cloud	Compatibility
Customer	Contact1:1	Fully supported
Customer (status = Prospect)	Lead1:many	Fully supported
Company/Dealer Account	Account1:1	Fully supported
Vehicle Deal	Opportunity1:1	Fully supported
Vehicle Inventory	Asset1:1	Fully supported
Service Record / Repair Order	Case1:1	Fully supported
F&I Product	Opportunity Line Itemmany:1	Fully supported
Parts Inventory	Product21:1	Mapping required
Staff / User	User1:1	Fully supported
Note / Document Attachment	ContentDocument / Note1:1	Fully supported
Custom Field (PBS user-defined)	Custom Field (__c)1:1	Fully supported
PBS Workflow / Automation	Salesforce Flow1:1	Fully supported

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

Salesforce Sales Cloud gotchas

High

Workflow Rules and Process Builder are retired

High

Bulk API batch quota exhaustion during large imports

Medium

Storage overage billing is non-obvious

Medium

Account-Contact many-to-many relationship mapping

Low

Territory and team member import ordering dependencies

PBS Systems gotchas		Salesforce Sales Cloud gotchas
Severity	Issue	Severity	Issue
High	No public data export API for self-serve migration	High	Workflow Rules and Process Builder are retired
Medium	Custom fields vary per dealership with no standard schema	High	Bulk API batch quota exhaustion during large imports
Medium	Service history links to parts and technicians require careful relationship mapping	Medium	Storage overage billing is non-obvious
		Medium	Account-Contact many-to-many relationship mapping
		Low	Territory and team member import ordering dependencies

Pair-specific challenges

Vehicle Deal to Opportunity Record-Type mapping requires pre-created Salesforce schema

PBS Vehicle Deals carry a deal_type field distinguishing New Vehicle, Used Vehicle, and Fleet transactions. Salesforce requires a separate Record Type for each deal type so that StageName pick-list values, page layouts, and validation rules can vary per vehicle category. Teams migrating without pre-creating Record Types will have all deals land with the default Record Type, mixing stage values across vehicle categories. We deliver a Record Type and page layout setup plan as part of the migration package so the Salesforce admin can pre-create the schema before data lands. Once the default Record Type is assigned to records, changing it requires a manual update or an Apex script.
F&I product selections flatten into OpportunityLineItems but Product2 records must pre-exist

PBS stores F&I products (GAP, paint protection, extended warranty) as sub-records attached to a Vehicle Deal. Salesforce represents these as OpportunityLineItems, which require a corresponding Product2 record with a StandardPrice defined. If the customer's Salesforce org does not have Product2 records for all F&I products before migration runs, those line items will fail to insert. We provide a Product2 creation checklist with PBS product names and prices during the planning phase so the admin can create them before the full migration runs.
Service RO numbers stored as Case.CaseNumber but PBS RO sequence may conflict with Salesforce auto-number

PBS Repair Order numbers follow the dealership's internal numbering sequence (e.g., RO-2024-01432). Salesforce auto-number Case.CaseNumber generates its own sequence and does not allow external ID assignment at insert time. We store the PBS RO number in a custom field (RO_Number__c) and map Case.CaseNumber to the next available Salesforce auto-number. The RO_Number__c custom field is indexed for search so service advisors can look up vehicles by the familiar PBS RO number in Salesforce.
PBS staff roles and department assignments map to Salesforce Profile and Role with manual decisions required

PBS staff records include a role field (Salesperson, Service Advisor, Parts Manager, etc.) and a department assignment. Salesforce separates Profile (controls field-level access and tab visibility) from Role (controls record visibility via hierarchy). There is no one-to-one mapping from PBS role names to Salesforce Profiles. We deliver a staff mapping worksheet where the admin assigns each PBS role to a Salesforce Profile and Role pair before migration, then we apply those assignments during user resolution.
PBS custom fields require manual pre-creation in Salesforce with correct field type and pick-list values

PBS supports user-defined custom fields on customer, vehicle, and service records. Each PBS custom field must be pre-created in Salesforce as a custom field with the __c suffix before migration validation runs. Field type must match (text, pick-list, number, date) and pick-list values must be replicated exactly. We include a custom field creation checklist in the migration plan with the field name, type, help text, and pick-list values for each custom field found in the PBS export.

Migration approach

Six steps for a successful PBS Systems to Salesforce Sales Cloud data migration

Inventory PBS export scope and extract via PBS Database Export Interface

Before migration begins, we work with your PBS team to run a full export using the PBS Database Export Interface. We inventory the record types present (Customer, Vehicle Deal, Service Record, Parts, Company, Staff) and estimate volumes for each. We also capture custom field definitions from PBS Setup. This scope document drives the custom field creation checklist and the Record Type setup plan delivered to your Salesforce admin before migration runs.
Pre-create Salesforce Record Types, custom fields, and Product2 records

Your Salesforce admin (guided by our checklist) creates the Record Types for each deal type (New Vehicle, Used Vehicle, Fleet), creates all custom fields on Contact, Account, Opportunity, Asset, and Case matching the PBS custom field definitions, and creates Product2 records for each F&I product with StandardPrice defined. We validate the setup against the scope document before proceeding to the sample migration.
Resolve PBS owners and staff to Salesforce Users by email match

PBS staff and owner email addresses are matched against Salesforce User records. Unmatched owners are flagged with the email address and PBS role so your admin can create Salesforce Users first or assign a fallback owner. No Opportunity or Case lands without a valid OwnerId. Staff records that do not have a Salesforce User are flagged in the migration report for manual follow-up.
Run sample migration with field-level diff on 200–500 representative records

We run a sample migration against a sandbox using a representative slice of PBS data spanning customers, companies, vehicle deals, assets, service records, and attachments. We generate a field-level diff report showing source value, mapped destination field, and destination value for every mapped field. You review the diff to verify Record Type assignment, F&I product line items, service RO number mapping, and owner resolution before the full migration is committed.
Execute full migration with delta-pickup window and audit logging

The full migration runs against your Salesforce production org. A delta-pickup window of 24–48 hours captures any PBS records modified during the cutover. Every operation is logged to an audit record (source record ID, destination record ID, operation type, timestamp). One-click rollback is available if reconciliation against the pre-migration count report fails. After rollback window closes, the audit log is delivered as a CSV for your records.

Platform deep dives

Context on both ends of the pair

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.

Salesforce Sales Cloud

Destination

Strengths

Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow.
Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer.
Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures.
Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization.
Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.

Weaknesses

Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price.
Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise.
Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant.
API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling.
Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

	PBS Systems Source	Salesforce Sales Cloud Destination
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.	Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow. Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer. Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures. Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization. Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.
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.	Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price. Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise. Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant. API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling. Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from PBS Systems to Salesforce Sales Cloud

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

PBS Systems

Salesforce Sales Cloud

How PBS Systems objects map to Salesforce Sales Cloud

What specifically takes care here

Six steps for a successful PBS Systems to Salesforce Sales Cloud data migration

Context on both ends of the pair

How hard is this migration?

Estimate your PBS Systems to Salesforce Sales Cloud migration cost

What are you migrating?

Frequently asked questions about PBS Systems to Salesforce Sales Cloud data migrations

Can't find your answer?

Related migrations to explore

Move from PBS Systems.
Land in Salesforce Sales Cloud, intact.

Migrate from PBS Systems to Salesforce Sales Cloud

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

PBS Systems

Salesforce Sales Cloud

How PBS Systems objects map to Salesforce Sales Cloud

What specifically takes care here

Six steps for a successful PBS Systems to Salesforce Sales Cloud data migration

Context on both ends of the pair

How hard is this migration?

Estimate your PBS Systems to Salesforce Sales Cloud migration cost

Frequently asked questions about PBS Systems to Salesforce Sales Cloud data migrations

Can't find your answer?

How long does a PBS Systems to Salesforce Sales Cloud migration take?

Will my PBS workflows and automation rules migrate to Salesforce Flow?

What does a PBS Vehicle Deal become in Salesforce?

Can I migrate PBS custom fields to Salesforce custom fields?

What happens to PBS service write-up records in Salesforce?

Does the migration affect my PBS account during cutover?

How do I handle PBS parts inventory in Salesforce?

What staff and user mapping is required before migration runs?

Related migrations to explore

Move from PBS Systems. Land in Salesforce Sales Cloud, intact.

Move from PBS Systems.
Land in Salesforce Sales Cloud, intact.