Migrate from Texada Software to Microsoft Dynamics 365 Sales

Texada customers map directly to Dynamics 365 Sales Accounts. Customer name becomes Account Name, phone and email flow to the primary contact fields, and the Texada customer type (dealer vs. renter) maps to a custom pick-list field on the Account record. Parent-child customer hierarchies in Texada map to the Account.ParentId hierarchy in Dynamics 365.

Texada contact records map to Dynamics 365 Sales Contacts 1:1. Each contact links to an Account via AccountId. Multiple Texada contacts associated with one customer become multiple Contact records under the same Account. Contact roles in Texada (billing, primary, service) map to the Dynamics 365 Contact.CustomerRoleCode field or a custom pick-list.

Texada equipment items — with serial numbers, manufacturer, model, year, condition code, meter-reading fields, and daily/weekly/monthly rental rates — map to Dynamics 365 Sales Products. The rental rate fields (daily_rate, weekly_rate, monthly_rate) become custom decimal fields on the Product record. Serial numbers migrate to the serial number field or a custom field if the standard field is not enabled.

This is the most complex object in the migration. Texada rental contracts have no native Dynamics 365 equivalent. We create a custom Rental_Contract__c table (or use the Opportunity record directly for simpler setups) with fields for contract_number, rental_start_date, rental_end_date, daily_rate, weekly_rate, monthly_rate, equipment_id, and return_status. The Opportunity.Amount field carries the total contract value; the custom table carries the rate structure.

Each line item on a Texada rental contract — specifying the equipment item, quantity, rate, and rental period — maps to an Opportunity Product record in Dynamics 365 Sales. The Opportunity Product carries unit price, quantity, and a manual discount field. If the rental term varies per line, a custom Rental_Term_Days__c field on the Opportunity Product captures the period.

Texada work orders — covering equipment service events, labor hours, parts used, and service-agreement links — map to a custom Work_Order__c table or Dynamics 365 Sales Cases depending on the volume and whether the service team uses the Cases module. Work order status, priority, and assigned technician fields map to custom fields or the native Case priority and owner fields. Service agreement links become a lookup to the custom Rental_Contract__c table.

Texada quotes that are in a pending or accepted state map to Dynamics 365 Sales Quotes linked to Opportunities. Accepted quotes roll the quote totals into the Opportunity Amount field. Rejected or expired quotes are optionally migrated as historical records with a closed status, stored as custom fields on the Opportunity for audit purposes.

Texada payments linked to rental contracts map to Opportunity Amount updates or Dynamics 365 Sales Invoice records depending on the accounts-receivable strategy. If the destination uses Dynamics 365 Business Central for AR, payments migrate as invoices linked to the Account. If AR stays in Texada or a third-party system, payments are recorded as Opportunity Amount updates with a custom Payment_Date__c field.

Texada vendor and supplier records map to Dynamics 365 Sales Accounts using a custom Is_Vendor__c boolean field or the Account.VendorTypeCode pick-list set to 'Vendor'. This approach consolidates all external parties — customers and vendors alike — within the same Account entity, enabling a unified contact management model and simplified lookup relationships across the CRM without requiring separate vendor-specific tables or duplicate contact records.

Texada notes and file attachments on contracts, work orders, and equipment records migrate to Dynamics 365 Sales Notes (rich text) and Attachments. Files are re-uploaded to the associated record's SharePoint document location or Dynamics 365 native file storage. Original timestamps and created-by users are preserved as metadata on the migrated note.

Texada operator and owner IDs are resolved by email match against Dynamics 365 Sales Users. Unmatched owners are flagged before migration and assigned to a fallback User record or held in a custom Unmatched_Owner__c field on the target record for manual assignment after go-live.

Texada tax tables and regional configuration are Texada-specific constructs. These cannot migrate directly. We export the Texada tax table data as a reference CSV for the Dynamics 365 Sales admin to re-enter in the system configuration, or recommend a third-party tax integration such as Vertex or Avalara.

Texada's general ledger chart of accounts is part of its integrated financials module. Dynamics 365 Sales does not include an accounting module; the chart of accounts must be configured in Dynamics 365 Business Central or a third-party ERP. We export the chart of accounts as a reference file for the ERP implementation team.