Migrate from STEL Order to Freshsales

STEL Order stores client name, company, phone, and email in one flat record. FlitStack AI splits this: the company name maps to a Freshsales Account, and the primary contact maps to a Freshsales Contact linked by AccountId. If the client is a solo entity, it becomes a Contact with no Account link.

STEL Order work orders are the primary operational record — they contain the client link, work order type, status, priority, scheduled date, assigned technician, location, and description. Freshsales has no native work order object. We map each STEL Order work order to a Freshsales Deal, with custom fields on the Deal capturing work order type, priority, status label, and the original work order number for traceability.

STEL Order jobs are line items or sub-tasks attached to a work order — they carry the service description, assigned technician, time entries, and client signature. One work order can contain multiple jobs. We map each job to a child Deal linked by a custom parent_work_order field, preserving the job description, scheduled date, and technician name. Jobs without a work order parent migrate as standalone Deals.

STEL Order product catalog (name, SKU, description, unit price, cost, sales unit) maps directly to Freshsales Products. Product bundles in STEL Order become individual Products in Freshsales — the bundle relationship is noted for manual rebuild in Freshsales if needed.

STEL Order assets track client equipment — warranty dates, model numbers, service history, and location. Freshsales has no native asset management module. We map assets to a custom module in Freshsales (Pro and Enterprise plans) linked to the Account, storing equipment name, serial number, warranty expiry, and last service date as custom fields.

STEL Order invoices are fully formatted financial documents with line items, tax rates, and payment status. Freshsales has no native invoicing module. Invoice metadata (invoice number, amount, date, status) migrates as a custom field on the related Deal. The full invoice document is preserved as a Note with a file attachment in Freshsales.

STEL Order quotes and estimates map directly to Freshsales Quotes, preserving the full sales proposal structure. The quote name, total monetary amount, validity expiration date, and current status (Sent, Accepted, Rejected, or Expired) transfer as native Freshsales Quote fields. Quote line items — each product or service with quantity, unit price, and discount — map to Freshsales Quote Items linked to the parent Quote record, maintaining the hierarchical pricing structure built in STEL Order.

STEL Order delivery notes document what was delivered as part of a work order. Freshsales has no native delivery note object. We migrate delivery note metadata (number, date, linked work order) as a custom field on the Deal and attach the delivery note document as a Note with a file in Freshsales.

STEL Order tracks stock levels per warehouse location with reorder thresholds. Freshsales Product Catalog has no inventory management. Stock levels, warehouse locations, and reorder settings migrate as a reference document for manual entry into an inventory system post-migration, or as a custom Inventory module in Freshsales Pro/Enterprise if your plan supports custom modules.

STEL Order team members and technicians are internal users who own work orders and jobs. They map to Freshsales Users by email resolution. The team_member_id, role, and team restrictions from STEL Order are stored as custom fields on the Freshsales User record for reference.

STEL Order records phone calls, emails, and notes attached to work orders and clients as part of the field-service communication log. Each logged call, sent email, and captured note maps to a Freshsales Task (for calls and emails) or Note record, with the original timestamp, owning technician name, and linked Deal or Contact record preserved to maintain the full communication history originally tracked in STEL Order.

STEL Order supports custom fields on client records to capture industry-specific data beyond standard fields. Each client-level custom field is recreated as a Freshsales custom field on the Contact or Account object, maintaining the same field type — whether text, number, dropdown, or date — and preserving any pick-list options or validation rules that were configured in STEL Order for consistent data entry.

STEL Order custom fields on work orders and jobs capture operational details like service category, contract type, or billing code. These custom fields map to Freshsales custom fields on the Deal object, preserving field type fidelity throughout the migration. Pick-list values become Freshsales dropdowns with matching options, date fields remain date fields, and text fields transfer directly without transformation.

STEL Order files attached to work orders, jobs, clients, and products are re-uploaded to Freshsales Files linked to the corresponding Contact, Account, or Deal record. The original filename and upload date are preserved. Files over 25MB are flagged for manual handling.

STEL Order workflows, notification rules, and automation triggers cannot migrate to Freshsales. Freshsales Automation Rules use a different event-action model. We export workflow definitions as a JSON reference document for your Freshsales admin to rebuild using Freshsales Automation Rules after migration.