Migrate from STEL Order to HighLevel

Job scheduling model has no direct HighLevel equivalent — technician assignment and GPS location require custom fields

STEL Order organizes work around jobs: technician assignment, scheduled date and time, GPS location, on-site photos, and client signature. HighLevel has no native job-dispatch or field-service model — it uses Tasks with due dates. During migration, FlitStack AI maps job technician to Assigned_Technician__c custom field (email-matched to a HighLevel user), GPS location to the task location field, and on-site description to the task note. Job status (scheduled, in_progress, completed, cancelled) becomes Job_Status__c custom pick-list. On-site photos and client signature images are stored as note attachments. HighLevel Tasks cannot display a map view of job locations natively; this requires a custom report or a third-party map integration post-migration.

STEL Order invoice lifecycle does not exist in HighLevel — invoice records become files with custom-field metadata

STEL Order manages the complete invoice lifecycle: PDF generation, payment tracking, Stripe and PayPal integration, and tax consultant login for accounting compliance. HighLevel has no native invoice object. FlitStack AI handles this gap by uploading every STEL Order invoice PDF as a HighLevel File attached to the relevant contact, and by storing invoice number (Invoice_Number__c), total (Invoice_Total__c), payment status (Invoice_Status__c), and due date (Invoice_Due_Date__c) as contact custom fields. Any Stripe or PayPal payment records linked to invoices in STEL Order are preserved as notes on the contact record. HighLevel Payments integration must be reconnected after migration if you use Stripe or PayPal to collect invoices — the existing connection credentials will not transfer.

STEL Order's Make/Integromat automations do not migrate — workflow definitions must be rebuilt in HighLevel's Workflow Builder

STEL Order uses Make (formerly Integromat) for automation — the STEL Order Make integration exposes triggers for new clients, orders, products, invoices, and delivery notes. HighLevel has its own Workflow Builder with a fundamentally different trigger-action model. FlitStack AI migrates data only; Make scenarios and STEL Order automations cannot be exported in a format compatible with HighLevel's Workflow Builder. We export every STEL Order workflow definition as a written reference document so your team can rebuild equivalent automations in HighLevel's Workflow Builder. The HighLevel Workflow Builder supports triggers on contact creation, pipeline stage changes, form submissions, calendar bookings, and custom field updates — your team maps STEL Order's automation logic to these triggers during rebuild.

HighLevel API 2.0 rate limits cap bulk migrations at 200,000 requests per day — large STEL Order datasets require staged batching

HighLevel API 2.0 enforces a limit of 200,000 API requests per day and 100 requests per 10 seconds per sub-account. STEL Order datasets with tens of thousands of records (clients + quotes + jobs + invoices + line items) can exceed this during a full migration run. FlitStack AI batches all write operations into staggered calls with automatic retry on 429 responses, and switches to HighLevel's Bulk CSV import path for contacts when API throughput is insufficient. We run a pre-migration API benchmark against your specific sub-account before the full migration to calibrate the batch window. If your STEL Order dataset exceeds 50,000 records, we schedule the migration in two passes: contacts and companies first, then opportunities and tasks in a second pass.

STEL Order team restrictions and role-based permissions do not map to HighLevel's permission model

STEL Order Lite plan includes team management with team restrictions — per-user seat limits and role-based access controls that govern what each team member can see and edit. HighLevel's permission model uses agency-level roles (Admin, Member, Starter) and sub-account access rules, which operate on a different logic than STEL Order's per-seat restrictions. Team restrictions defined in STEL Order do not transfer automatically. FlitStack AI surfaces the full list of STEL Order team roles and their assigned permissions before migration. Your HighLevel admin must recreate access rules in HighLevel's User Roles settings post-migration. We provide a role-mapping worksheet that lists every STEL Order role alongside its nearest HighLevel permission equivalent.