Migrate from STEL Order to Salesforce Sales Cloud

STEL Order Clients map to Salesforce Accounts for business entities and Contacts for individual points of contact. Address fields, email, and phone move directly. A Client's primary contact role is recorded in Salesforce Contact with AccountId as the lookup. If the Client has multiple contacts, secondary contacts load as additional Salesforce Contact records linked to the same Account.

STEL Order Products map to Salesforce Product2 records (Name, Product Code, Description). Each Product2 gets PricebookEntry records tied to the org's active Pricebook so Opportunities and Orders can reference unit prices. Discontinued or archived products in STEL Order become Inactive Product2 records to preserve historical invoice line items.

STEL Order Quotes become Salesforce Opportunities at the 'Proposal/Price Quote' stage, or Quote objects if Salesforce CPQ is licensed. Quote line items map to OpportunityLineItems or QuoteLineItems. STEL Order quote statuses (Draft, Sent, Accepted) map to Salesforce Opportunity Stage values chosen by your admin during schema planning.

STEL Order Work Orders have no direct Salesforce equivalent. The migration plan offers two paths: (1) Case for service-desk style work orders linked to the Account Asset, or (2) a custom Work_Order__c object created before migration with fields mirroring STEL Order's schema. Work_Order__c is the recommended path for field service companies because it preserves STEL Order's full operational fields without forcing service-desk semantics onto operational jobs.

STEL Order Jobs are discrete operational activities tied to a Work Order. They map to Salesforce Tasks (checklist-style) or Events (time-block style) based on whether STEL Order records a start/end time. For companies with complex job hierarchies, a custom Job__c object with a lookup to Work_Order__c preserves the STEL Order relationship model.

STEL Order Invoices with payment status, due dates, tax amounts, and line items require a custom Invoice__c object in Salesforce because the standard Order object assumes a quote-to-cash flow that STEL Order's invoice model does not follow. Invoice_Line_Item__c as a child custom object maps STEL Order line items with product, quantity, unit price, and tax.

STEL Order Assets map 1:1 to Salesforce Asset objects. The serial number, installation date, location, and linked Client map to Salesforce Asset's Name, InstallDate, Location, and AccountId. Warranty end date migrates as a custom Warranty_End_Date__c field on the Asset record. Linked equipment photos are saved as Salesforce Files attached to the Asset record.

STEL Order Team Members with name, email, phone, role, and active status map to Salesforce Users. Email is the key field for owner resolution — FlitStack matches each STEL Order owner email to a Salesforce User email to set OwnerId on migrated records. Inactive STEL Order members flagged for exclusion or archived without a Salesforce user are logged for admin decision.

STEL Order documents attached to jobs, work orders, or invoices are downloaded and re-uploaded as Salesforce Files linked to the corresponding migrated record. File size limits of 25MB per file apply (Salesforce default). Photos captured in the STEL Order mobile app attach to the Job or Work Order Salesforce record as ContentDocument links.

Every STEL Order custom property on every object requires a corresponding custom field on the Salesforce target object. Field data type is inferred from STEL Order's property type (text, number, date, pick-list). The migration plan lists every custom property with its target field name, data type, and pick-list value mapping so your Salesforce admin can pre-create fields in Setup before the data load runs.