Migrate from STEL Order to Twenty CRM

STEL Order customers map 1:1 to Twenty People records. Email, phone, address, and job title transfer directly. STEL Order associates each customer with one primary company, which resolves as a companyId lookup in Twenty. Multi-contact-per-company scenarios collapse to one primary company assignment, with secondary associations flagged for manual review.

STEL Order company records map directly to Twenty Companies. Company name, domain/website, industry, employee count, and annual revenue transfer as-is. Parent-company hierarchies in STEL Order map via Twenty's Parent Company relation field. Companies must be migrated before People to satisfy Twenty's foreign-key constraint on the companyId lookup.

STEL Order jobs are the most complex object to map. They translate to Twenty Opportunities with the job name as Opportunity title, job amount as Opportunity amount, and close date from the job's scheduled date. Job status values require explicit value mapping to Twenty's opportunity stage pick-list — e.g. 'In Progress' maps to a defined stage name in Twenty's Sales Process. We apply a default stage value and flag for admin confirmation before the full run.

STEL Order's custom job statuses (e.g. Pending, Scheduled, In Progress, Completed, Cancelled) have no native equivalent in Twenty's opportunity stage model. We map each distinct status to a corresponding Twenty stage value, preserving the original status label in a custom field (Original_Job_Status__c) for audit continuity. If STEL Order uses more stages than Twenty's default, we create additional stage values in Twenty before the migration runs.

STEL Order work orders contain job details, line items, technician notes, and attachments. We convert each work order to a Note attached to the corresponding Twenty Opportunity (mapped from the parent job). The Note body contains the work order description, line item summary, and technician comments. Attachments are re-uploaded to Twenty's file storage and linked to the Note record.

STEL Order estimates and quotes migrate as Notes on the related Opportunity, containing the full estimate text and line items as structured plain text. Amount and expiry date from the estimate transfer as custom fields on the Note. PDF attachments from estimates are re-uploaded as Twenty Files. Financial document generation is not replicated — Twenty does not include native quote-to-PDF functionality.

STEL Order custom fields on Customers, Jobs, and Companies map to custom fields on Twenty People, Opportunities, and Companies respectively. Text, number, date, and email custom fields translate directly. Pick-list (select) fields require manual value creation in Twenty's field settings before migration — we provide a value-mapping spreadsheet. Multi-select fields map to Twenty's multi-select field type.

STEL Order users and technicians resolve to Twenty Workspace Members by email match. Unmatched owners are flagged before migration for manual assignment in Twenty's workspace settings. Once users exist in Twenty, ownerId on Opportunities and Tasks resolves via the email lookup. STEL Order role and permission structures do not migrate — Twenty's role and permission system must be configured separately.

STEL Order product and inventory items have no direct Twenty CRM equivalent — Twenty is a CRM, not an inventory or ERP system. We export products as rows in a CSV for reference and advise on a separate inventory management tool if needed. For teams using STEL Order products as the basis for quotes, we preserve product names in a custom text field on the Opportunity for manual reference.

Documents attached to STEL Order jobs, work orders, and customers (e.g. photos, PDFs, signed work notes) are downloaded and re-uploaded to Twenty's file storage. Files attach to the corresponding Twenty record (Person, Company, or Opportunity). File size limits and MIME-type restrictions apply per Twenty's storage configuration. We flag any file that exceeds Twenty's supported size threshold for manual handling.

STEL Order invoices do not have a billing counterpart in Twenty CRM — Twenty has no native invoicing module. We attach invoice PDFs as files on the related Opportunity (from the parent job) and preserve invoice number, amount, and status as custom fields on the Note for financial reference. Invoice reconciliation must be handled outside of Twenty.

STEL Order workflows (job-routing rules, status-change triggers, notification automations) are business logic constructs that cannot be extracted and replayed in Twenty. We export the full workflow definition as a JSON specification document and a step-by-step guide for rebuilding each rule in Twenty's workflow builder. This is a manual step for your Twenty admin post-migration.