Migrate from PBS Systems to Microsoft Dynamics 365 Sales

PBS customer records contain both person and household data. We split into Dynamics 365 Account (for household or business buyer) and Contact (for the individual buyer). If PBS customer is a business, Account gets the business name; if consumer, Contact gets person fields and links to a default household Account.

Business-type PBS customers with company names, fleet accounts, or dealer-to-dealer transactions map directly to Dynamics 365 Account records. Primary buyer contact within the business maps as a related Contact with AccountId lookup. PBS fleet account terms and credit limits transfer as custom fields on the Account.

PBS vehicle records have no Dynamics 365 native equivalent. We create a Vehicle__c custom table with fields for VIN, stock number, year, make, model, trim, color, status (new/used/演示), location (lot or service bay), and acquisition cost. Vehicle__c links to Opportunity via a custom lookup field so each deal can reference the specific unit.

A PBS deal record bundles customer, vehicle, trade-in, F&I products, and payment structure. We transform this into a Dynamics 365 Opportunity (core deal), a Quote (F&I product selections with pricing), and an Order (final deal structure if closed-won). The Opportunity gets the vehicle as a custom lookup, trade-in as a line item with negative amount, and F&I products as additional quote/order lines.

PBS F&I products (GAP, maintenance contracts, warranties, credit life) are stored as deal-level selections with pricing. These map to Dynamics 365 Quote Product line items. Each F&I product type gets a value-mapping entry to the corresponding product catalog item. If PBS F&I products don't exist in Dynamics, we create them as products before populating quote lines.

Trade-in vehicles in PBS deals are separate records linked to the deal. We create a Quote Product line with the trade-in vehicle as a line item with a negative amount (the allowance). The trade-in VIN and year/make/model transfer as description text on the line. If PBS stores trade-in condition details, we preserve those in a custom field on the Quote Product.

PBS service ROs have no native CRM equivalent. We create Service_RO__c as a custom table with RO number, open/close date, status, advisor, technician, service type, labor hours, and total cost. Individual line items (parts used, labor operations) store in a related Service_RO_Line__c table. Open ROs generate a Task on the vehicle owner Contact for follow-up. Historical service records migrate as completed Service_RO__c entries.

PBS parts inventory consists of part numbers, descriptions, bin locations, on-hand quantity, and cost. We map parts to Dynamics 365 Product records with product type = Inventory. On-hand quantities and bin locations store in a custom Inventory_Location__c table linked to Product. Parts transactions (receiving, selling to RO, returning) migrate as Inventory_Transaction__c records for reporting continuity.

When a PBS parts inventory item is used on a service RO, we link the Product record to the corresponding Service_RO_Line__c entry. The part number, quantity used, and cost transfer as line item details. This preserves the parts cost breakdown within each service RO for F&I and service margin reporting.

PBS internet leads and showroom prospects tracked in the CRM module map directly to Dynamics 365 Lead records. Source of lead (website, walk-in, phone) transfers as a custom field. Lead status (new, contacted, sold, lost) maps via value mapping to Dynamics Lead Status options. If PBS stores lead scoring, we preserve it as a custom numeric field.

PBS records phone calls, emails, and meetings tied to customers and deals. Phone call logs map to Dynamics 365 Task records with Type = Phone Call. Emails can be stored as email Activities in Dynamics or linked to Exchange via server-side sync. Meetings map to Dynamics 365 Events with original start/end times and location preserved.

PBS staff records (salespeople, service advisors, parts counter employees) map to Dynamics 365 SystemUser records by email match. If PBS staff IDs are linked to deals and service ROs, we preserve the PBS staff ID as a custom field on the SystemUser for audit traceability. Unmatched PBS staff are flagged before migration — either invite to Dynamics or assign records to a fallback owner.

Multi-store PBS deployments require Dynamics 365 to distinguish between locations. We create a Business_Unit__c custom table with store name, address, and PBS location code. Accounts, Opportunities, and Service_RO__c records each get a Business_Unit__c lookup so reports can filter by store. Dynamics 365 Business Unit security roles can also be configured per location if needed.

PBS stores deal documents (contracts, F&I forms, service invoices) as attachments. We re-upload these to Dynamics 365 SharePoint integration if configured, or attach directly to the Opportunity/Service_RO__c record. File size limits apply — documents over 25MB are flagged for chunked upload or alternative storage reference.