CRM migration

Migrate from PBS Systems to Freshsales

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

PBS Systems logo

PBS Systems

Source

Freshsales

Destination

Freshsales logo

Compatibility

92%

11 of 12

objects map 1:1 between PBS Systems and Freshsales.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How PBS Systems objects map to Freshsales

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

maps to

Freshsales

Contact / Lead

1:many
Fully supported

PBS 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

maps to

Freshsales

Custom fields on Contact

1:1
Fully supported

PBS 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

maps to

Freshsales

Account

1:1
Fully supported

PBS 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

maps to

Freshsales

Deal

1:1
Fully supported

PBS 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

maps to

Freshsales

Custom Object / Task chain

1:1
Fully supported

PBS 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

maps to

Freshsales

Custom Object / Deal Product

1:1
Fully supported

PBS 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

maps to

Freshsales

Freshsales User

1:1
Fully supported

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

maps to

Freshsales

Task / Event

1:1
Fully supported

PBS 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

maps to

Freshsales

Custom fields on Deal

1:1
Fully supported

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

maps to

Freshsales

Freshsales Custom Fields

1:1
Fully supported

Any 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

maps to

Freshsales

Custom fields on Deal

1:1
Fully supported

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

maps to

Freshsales

Freshsales Files / Attachments

1:1
Fully supported

PDFs, 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.

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Automotive-specific data fields require custom field creation in Freshsales before migration

    PBS stores VIN, stock number, trade-in value, and service RO data as native DMS properties. Freshsales has no native automotive object model — there is no Vehicle or Service_RO object. Every automotive field from PBS needs a corresponding Freshsales custom field created on Contact, Deal, or a custom Service_RO__c object before migration data can land. If these custom fields are not pre-created, the migration plan flags them as blocking dependencies. FlitStack delivers a custom field creation checklist as part of the schema setup step so Freshsales is ready before the data runs.

  • PBS automations and dealership workflows do not migrate and must be rebuilt in Freshsales

    PBS v10 APEX includes service dispatch rules, parts reordering triggers, and sales desk F&I workflow steps that are tied to DMS events (RO status changes, deal stage transitions, financing submission). Freshsales Workflows operate on a different trigger model (record creation, field changes, form submissions) and have no compatibility with PBS automation logic. There is no export format for PBS workflows that maps to Freshsales Workflows. We can export PBS workflow definitions as a written reference for your Freshsales admin to use during the rebuild step after go-live, but the automation logic itself must be recreated manually in Freshsales's Workflow builder.

  • Multi-vehicle PBS customers collapse to primary vehicle in Freshsales Contact custom fields

    PBS allows a single customer record to have multiple vehicles associated — each with its own VIN, stock number, and service history. Freshsales Contact stores one set of custom vehicle fields per record. When a PBS customer has more than one vehicle, we map the primary (most recently updated) vehicle to the Contact's custom fields and store additional vehicles as a serialized JSON string in a long-text custom field Additional_Vehicles__c. This preserves the data but requires a manual review step if the team needs each vehicle to appear as a separate record in Freshsales.

  • PBS built-in phone and calling numbers do not transfer to Freshsales

    If the PBS team uses PBS's built-in phone system or any telco integration for outbound calls, those phone numbers and call records do not port to Freshsales. Freshsales includes built-in telephony (Freshcaller) on all plans, but call history and assigned phone numbers are Freshsales-specific and cannot be imported from PBS. Call recordings attached to PBS deal records may be stored as file attachments on the Contact or Deal, but Freshsales does not have a native call recording player — they function as downloadable files only.

  • F&I product bundles and deal jacket metadata require custom field design

    PBS deal jackets store F&I product selections (GAP, tire protection, extended warranty, credit life), financing term, and interest rate as structured fields within the deal record. Freshsales Deal object has no native F&I product fields. We map these to custom text, number, and currency fields on the Freshsales Deal (F_I_Product__c, F_I_Term_Months__c, Finance_Rate__c). If a PBS deal jacket contains more than five F&I product lines, we store the full bundle as a JSON string in a long-text field. The team should review whether they want these fields visible on the Deal layout or kept as reference-only.

Migration approach

Six steps for a successful PBS Systems to Freshsales data migration

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

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

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

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

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

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.
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

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

  • 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 Freshsales 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 Freshsales data migrations

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

Can't find your answer?

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 consultation

Most PBS-to-Freshsales migrations complete within 48–72 hours of clock time for setups under 50,000 records. Larger dealerships with 500k+ records — particularly those with extensive service RO history or multiple F&I product lines per deal — extend to 5–7 days. The longest planning step is creating Freshsales custom fields for automotive data (VIN, stock number, trade values, service ROs) before the data runs; FlitStack delivers the field creation checklist during discovery so Freshsales schema is ready before the migration begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from PBS Systems.
Land in Freshsales, 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