CRM migration
Field-level mapping, validation, and rollback between PBS Systems and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
PBS Systems
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between PBS Systems and Freshsales.
Complexity
BStandard
Timeline
48–72 hours
Overview
PBS Systems is a dealership management system (DMS) built around the automotive sales, service, and parts workflow — its CRM module is purpose-built for that context but lacks the pipeline flexibility, lead scoring, and AI-powered deal intelligence that modern sales teams require. Freshsales is a general-purpose SMB CRM from Freshworks that stores Leads, Contacts, Accounts, Deals, Tasks, and Events, with a custom field model that can accommodate automotive-specific properties. The migration carries PBS customer records, company/dealership data, active deals, and activity history into Freshsales's standard objects, while PBS's automotive fields — VIN, stock number, trade-in value, service RO history — are recreated as Freshsales custom fields on Contact and Deal. PBS automations and workflows do not transfer; those must be rebuilt in Freshsales's Workflows builder after go-live. We use PBS's export API and Freshsales's REST API to perform the data transfer, with a sample migration and field-level diff before the full run commits.
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 Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
PBS Systems
PBS Customer Record
Freshsales
Contact / Lead
1:manyPBS customer records migrate to Freshsales Contact if they represent an active customer relationship (vehicle sold, service history, or open deal). Records in PBS with no deal or service activity and no closed-won deal route to Freshsales Lead. The split is determined by the presence of any deal stage 'won' or any service RO in the PBS account history.
PBS Systems
PBS Vehicle Profile
Freshsales
Custom fields on Contact
1:1PBS stores vehicle year, make, model, VIN, and stock number as properties attached to a customer record. Since Freshsales has no native automotive vehicle object, we create custom text fields Vehicle_VIN__c, Vehicle_Make_Model__c, and Vehicle_Stock_Number__c on the Contact record. If a PBS customer has multiple vehicles, the primary (most recent) vehicle maps to these fields; additional vehicles are stored as JSON in a long-text custom field.
PBS Systems
PBS Company / Dealership Account
Freshsales
Account
1:1PBS company records representing commercial accounts, fleet buyers, or dealer-to-dealer relationships map directly to Freshsales Account. Dealership-level metadata (address, primary contact name, phone) maps to Account fields. Dealership name maps to Account Name, address fields map to the standard address compound on Account.
PBS Systems
PBS Deal / Deal Jacket
Freshsales
Deal
1:1PBS deal records carry deal value, stage, and F&I product selections. Deal amount maps to Freshsales Deal Amount; deal stage maps to Freshsales Deal Stage with a value-by-value map from PBS stage names to Freshsales stage names. F&I product selections and term details are stored as custom text fields on the Freshsales Deal because Freshsales does not have a native F&I product object.
PBS Systems
PBS Service RO
Freshsales
Custom Object / Task chain
1:1PBS service repair orders (ROs) are detailed records with line items, advisor assignment, and timestamps. Since Freshsales has no native service RO object, we create a custom object Service_RO__c in Freshsales and link it to the Contact record via a lookup relationship. Each RO number, date, status, and total maps to fields on the Service_RO__c record.
PBS Systems
PBS Parts Invoice
Freshsales
Custom Object / Deal Product
1:1PBS parts invoice line items map to Freshsales Deal Products if attached to a deal, or to a custom object Parts_Invoice__c linked to the Contact. Part number, description, quantity, and price map to custom fields on the respective object. Standalone parts invoices without a deal association are linked to the Contact's account.
PBS Systems
PBS Sales Rep / Owner
Freshsales
Freshsales User
1:1PBS staff records (sales rep, service advisor, parts counter) map to Freshsales users by email match. Each PBS staff member's email address is matched against Freshsales user accounts; unmatched owners are flagged before migration so the team can provision Freshsales seats or assign to a fallback user. Owner history on deals and ROs is preserved by storing the PBS owner name in a custom field.
PBS Systems
PBS Activity Log (calls, notes, emails)
Freshsales
Task / Event
1:1PBS records service advisor notes, sales call logs, and customer communications with timestamps and staff attribution. These migrate to Freshsales Tasks (for calls and notes) and Events (for scheduled meetings or RO review appointments). Original timestamps, subject lines, and owner assignments are preserved. Task Type field is set to 'Call', 'Note', or 'Email' based on the PBS activity category.
PBS Systems
PBS Trade-In Vehicle
Freshsales
Custom fields on Deal
1:1Trade-in vehicle details attached to a PBS deal jacket (year, make, model, mileage, value) map to custom text and currency fields on the Freshsales Deal record: Trade_In_Vehicle__c, Trade_In_Mileage__c, and Trade_In_Value__c. This preserves the trade-in context in Freshsales without needing a separate vehicle object.
PBS Systems
PBS Custom Fields (user-defined properties)
Freshsales
Freshsales Custom Fields
1:1Any PBS user-defined fields on Customer, Deal, or Service RO records that do not map to a standard Freshsales field are created as Freshsales custom fields in the appropriate data type (text, number, date, currency, picklist) before migration. We audit the full PBS custom field inventory during discovery and deliver a custom field creation checklist as part of the schema setup plan.
PBS Systems
PBS Financing / F&I Product
Freshsales
Custom fields on Deal
1:1F&I product selections (GAP, paint protection, extended warranty, term length, finance rate) stored in a PBS deal jacket are recreated as custom fields on the Freshsales Deal: F_I_Product__c (text), F_I_Term_Months__c (number), Finance_Rate__c (number). The F&I product bundle is stored as a JSON string in a long-text field if the number of product lines exceeds Freshsales custom field budget.
PBS Systems
PBS Attachments / Documents
Freshsales
Freshsales Files / Attachments
1:1PDFs, images, and documents attached to PBS deals, ROs, or customer records are downloaded from PBS storage and re-uploaded to Freshsales as Files attached to the corresponding Contact or Deal record. File size limits for Freshsales apply (25MB per file). Inline images in PBS notes are extracted and re-hosted as Freshsales attachments.
| PBS Systems | Freshsales | Compatibility | |
|---|---|---|---|
| PBS Customer Record | Contact / Lead1:many | Fully supported | |
| PBS Vehicle Profile | Custom fields on Contact1:1 | Fully supported | |
| PBS Company / Dealership Account | Account1:1 | Fully supported | |
| PBS Deal / Deal Jacket | Deal1:1 | Fully supported | |
| PBS Service RO | Custom Object / Task chain1:1 | Fully supported | |
| PBS Parts Invoice | Custom Object / Deal Product1:1 | Fully supported | |
| PBS Sales Rep / Owner | Freshsales User1:1 | Fully supported | |
| PBS Activity Log (calls, notes, emails) | Task / Event1:1 | Fully supported | |
| PBS Trade-In Vehicle | Custom fields on Deal1:1 | Fully supported | |
| PBS Custom Fields (user-defined properties) | Freshsales Custom Fields1:1 | Fully supported | |
| PBS Financing / F&I Product | Custom fields on Deal1:1 | Fully supported | |
| PBS Attachments / Documents | Freshsales Files / 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
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Audit PBS data model and deliver custom field schema for Freshsales
We extract a full inventory of PBS objects, fields, and relationships from the CRM module — including all custom fields, service RO structure, and F&I product fields. We cross-reference this against Freshsales's standard object model and produce a custom field creation checklist: which Freshsales custom fields to create on Contact, Deal, and Service_RO__c, what data type each field requires, and which PBS fields map to which Freshsales fields. This schema plan must be executed in Freshsales before migration data lands.
Resolve PBS staff records to Freshsales user accounts by email
PBS staff members (sales reps, service advisors, parts counter) are mapped to Freshsales users by matching email addresses. We pull the PBS staff list and compare it against the Freshsales user directory. Any PBS owner without a matching Freshsales account is flagged as a blocking dependency — the team provisions the Freshsales seat or assigns a fallback owner before migration runs. No deal, RO, or activity lands without a valid Freshsales owner.
Migrate accounts before contacts, then deals with automotive custom fields
We sequence the migration so foreign keys resolve correctly: PBS Company records migrate to Freshsales Accounts first, then PBS Customer records migrate to Freshsales Contacts (or Leads for inactive prospects) with vehicle VIN, stock number, and trade-in value mapped to Contact custom fields, then PBS Deals migrate to Freshsales Deals with F&I product fields, finance term, and stage mapping applied. Service ROs are written to the Service_RO__c custom object and linked to the parent Contact by the PBS customer ID.
Run a sample migration with field-level diff
A representative slice of 100–500 records — spanning contacts with multiple vehicles, deals with F&I bundles, and service ROs — migrates first. We generate a field-level diff between the PBS source values and the Freshsales destination fields so you can verify VIN mapping, F&I field population, RO linkage, and owner resolution before the full run commits. Any field that maps incorrectly is corrected in the mapping plan before the full migration runs.
Cut over with delta-pickup for in-flight records
The full migration runs against Freshsales using the validated field mapping. A delta-pickup window (typically 24–48 hours after the primary run) captures any records modified in PBS during the cutover — new service ROs, updated deals, or new contacts created by staff still working in PBS. Audit logs record every operation, and one-click rollback is available if reconciliation against the PBS source data fails.
Platform deep dives
PBS Systems
Source
Strengths
Weaknesses
Freshsales
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 Freshsales.
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 Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your PBS Systems to Freshsales 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 Freshsales
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.