Migrate from Texada Software to Salesforce Sales Cloud

Texada stores customer name, billing address, and contact details in one customer record. FlitStack splits this into a Salesforce Account for the business entity and a Contact for the primary buyer or operations contact. The Texada customer number maps to Account.AccountNumber for traceability.

Texada equipment records map directly to Salesforce Asset. Serial number maps to Asset.SerialNumber, make and model map to custom fields (Make__c, Model__c), and equipment status maps to Asset.Status. Meter readings at time of migration are stored in Meter_Reading__c custom Number field.

Rental contracts with billing cycles and rate codes map to Salesforce Contract for the legal agreement and Opportunity for the revenue pipeline view. Rate code values (daily, weekly, monthly) map to a custom Rate_Code__c pick-list on Contract. Line items for equipment on contract map to OpportunityLineItems.

Sales orders for equipment units map to Salesforce Opportunity with record type 'Equipment Sale'. CloseDate reflects the sale close date, Amount reflects the quoted sale price, and Stage reflects the order fulfillment stage (Proposal, Negotiation, Closed Won). This mapping preserves the full sales pipeline view in Salesforce for accurate forecasting and revenue reporting.

Texada service work orders map to Salesforce Cases. Work order number maps to Case.CaseNumber, status maps to Case.Status, priority maps to Case.Priority, and description maps to Case.Description. Technician assignment resolves by email match to Salesforce users via Case.OwnerId, ensuring the assigned technician can access their work order queue immediately after migration.

Texada work order parts and labor lines have no direct Salesforce equivalent. FlitStack creates a custom Work_Order_Line__c object linked to Case via a lookup, with fields for line_type__c (pick-list: Parts, Labor), part_number__c, quantity__c, and hours__c. This preserves the full parts-and-labor breakdown for billing reconciliation.

Texada vendors map to Salesforce Accounts using a 'Vendor' record type to distinguish them from customer accounts. Vendor tax ID maps to Account.Tax_Identification_Number__c. Primary contact at vendor maps to Account's primary Contact. This ensures vendor records are properly segmented from customer accounts for accurate ERP integration and procurement workflows.

Texada parts and products map to Salesforce Product2 with part number stored in Product2.ProductCode. Pricing from Texada rate codes is loaded as PricebookEntry records linked to the standard or custom pricebook. Inventory levels at migration time are stored in a custom Inventory_On_Hand__c field on Product2.

Texada G/L chart of accounts has no native Salesforce equivalent. FlitStack creates a custom GL_Account__c object with fields for account_number__c, account_name__c, and account_type__c, linked to Contract or Expense records via lookup. This preserves G/L mapping for ERP reconciliation without modifying Salesforce's standard accounting model.

Texada WorkFlow forms, conditional routing rules, and automated approval chains do not migrate. FlitStack exports WorkFlow definitions as JSON documentation so the Salesforce admin can reference the original routing logic when building equivalent Flows. Workflow rebuild is always a separate configuration engagement.