Migrate from Texada Software to HubSpot

Texada customers with an account number map to HubSpot Contacts. Texada stores contact-level details (name, phone, email, address) as properties on the customer record — these map directly to HubSpot's standard Contact properties. Texada customers without an email address require a placeholder email for HubSpot's import requirements, flagged before migration.

Texada's primary customer identifier is the account number. HubSpot has no native account-number field on Contact. We create a custom string property (Account_Number__c or Texada_Account_Number) and store the source account number on every migrated Contact for traceability and reconciliation against Texada records.

Texada supports multi-division setups where each division or branch is a separate operating entity. We map each Texada division to a HubSpot Company record, preserving the division name, address, and phone. Company-to-Contact associations are built after Contacts land so each Contact links to its parent Company via HubSpot's native association model.

Texada rental contracts store term length, billing cycle frequency, start and end dates, and line-item equipment. We map contracts to HubSpot Deals where the Deal name reflects the contract number or customer name + equipment description, the amount reflects the contract value, and custom properties carry term length in months and billing frequency (weekly, monthly, cycle-billed). Contract line items migrate as Deal custom property lists or as a custom Contract_Lines__c custom object linked to the Deal.

Texada automates cycle billing (weekly, bi-weekly, monthly) on rental contracts. HubSpot has no native billing-cycle field. We create Billing_Cycle__c (picklist: Weekly, Bi-Weekly, Monthly, Quarterly) and Contract_Term_Months__c (number) as custom properties on the Deal so billing operations teams can filter contracts by cycle in HubSpot without a separate billing module.

Texada tracks equipment with serial number, asset tag type, status code, and location. HubSpot has no native asset-tracking object. We create a custom object (Equipment_Asset__c) with fields for Serial_Number__c, Asset_Tag__c, Status__c, Location__c, and Equipment_Description__c. Each asset is linked to its owning Customer (Company) and any active Contract (Deal) via HubSpot custom-object associations.

Texada service management generates work orders linked to equipment and customers. We create a Work_Order__c custom object with fields for work order number, status, scheduled date, labor hours, and description. Work_Order__c links to the Equipment_Asset__c (for the equipment being serviced) and to the Contact/Company (for the customer). Original work-order create dates are preserved as custom datetime fields for service-history continuity.

Texada's parts and service quoting generates estimates tied to work orders or contracts. In HubSpot, service quotes can be stored as a custom Quote__c custom object with line items (Part_Number__c, Quantity__c, Unit_Price__c) linked to the related Deal or Work_Order__c. If the quote is attached to a rental contract, it links to the Deal representing that contract.

Texada operators managed under Texada Identity Service (TIS) map to HubSpot users by email address. TIS supports email-based operator accounts — we match TIS operator emails to existing or invited HubSpot users. Unmatched operators are flagged and assigned to a fallback HubSpot user (e.g., the admin) so no migrated record lands without an owner.

Texada SRM holds full accounts receivable, invoicing, and G/L transaction history tied to contracts. HubSpot CRM does not store financial transactions natively. We preserve Texada transaction data (invoice number, amount, date, status) as a read-only custom object (Transaction__c) linked to the related Deal/Contract. Your accounting team uses Texada or a dedicated accounting tool for transaction reporting — this custom object provides a reference trail in HubSpot.

Texada supports file attachments and notes on customers, contracts, and work orders. Files re-upload to HubSpot Files (or the relevant Contact/Company/Deal record). Notes map to HubSpot's Notes tool with original timestamps and owner preserved. File size limits apply per HubSpot's import constraints; large files are flagged before migration.

Texada Analytics dashboards and SRM reports do not have HubSpot equivalents. Underlying data migrates but the dashboards themselves must be rebuilt in HubSpot's reporting module. We provide a data dictionary of migrated fields so your HubSpot admin can reconstruct key reports in HubSpot Analytics after migration.