Migrate from Swivl Tech to Salesforce Sales Cloud

Swivl Tech customers are company-level records containing company name, address, phone, and billing contact. FlitStack maps these to Salesforce Accounts. Company-level address fields on the Swivl customer record become Account.Address fields. Billing contact details migrate as a related Contact record under the Account.

Swivl Tech contact sub-objects (first name, last name, email, phone, role) map 1:1 to Salesforce Contact fields. The Contact's AccountId is set by resolving the parent Swivl customer to its migrated Salesforce Account. If no parent customer exists, the Contact attaches to a default 'Unassigned Accounts' record.

Swivl Tech work orders are the central service record — they contain job status, scheduled date, assigned technician, line items, and asset linkage. FlitStack maps these to Salesforce Cases in the first instance. For orgs requiring richer schema, we create a custom Work_Order__c object with Status__c, Scheduled_Date__c, Technician__c (lookup to User), and Asset__c fields that mirror Swivl's structure.

Swivl Tech work order statuses (Scheduled, In Progress, On Hold, Completed, Cancelled) map value-by-value to Salesforce Case Status pick-list values (New, Working, On Hold, Closed, Cancelled). Custom statuses require Salesforce admin to pre-create the pick-list values in the target org before the migration runs.

Swivl Tech technicians are user records with name, email, phone, and service-territory fields. FlitStack resolves each Swivl technician by email match against existing Salesforce Users. Unmatched technicians are flagged before migration; the team either creates Salesforce users or assigns work orders to a fallback owner. Technician service territories in Swivl map to Salesforce Territories if the org has Territory Management enabled.

Swivl Tech work orders contain line items (service description, quantity, unit price, total). If invoices represent billable service opportunities, line items merge into Salesforce Opportunity Products linked to the parent Case-as-Opportunity. If invoices are historical financial records, they migrate as a custom Invoice_Line_Item__c object with a lookup to the migrated Account.

Swivl Tech assets (equipment name, serial number, location, linked customer) map to Salesforce's standard Asset object when the target org has Asset tracking enabled. Asset fields include Name, AccountId (linked to migrated customer), SerialNumber, InstallDate, and Status. If Salesforce Asset is disabled, FlitStack creates a custom Asset__c object preserving the full Swivl asset schema.

Swivl Tech invoices carry invoice number, issue date, due date, total amount, payment status, and line items. Sales Cloud has no native invoice object. FlitStack migrates invoices as a custom Invoice__c record (Invoice_Number__c, Invoice_Date__c, Due_Date__c, Total_Amount__c, Payment_Status__c) linked to the Account. Line items are migrated as related Invoice_Line_Item__c records.

Swivl Tech custom properties on any object map to Salesforce custom fields with the __c suffix. Before migration, FlitStack generates a schema setup plan specifying the field label, data type, pick-list values, and field-level security for each custom property. The Salesforce admin creates these fields before the data load phase begins.

Swivl Tech attachments and photos on work orders or assets are downloaded and re-uploaded to Salesforce Files, linked to the migrated record (Case or Asset). File size limits apply — Salesforce default is 25MB per file. Inline images in notes are extracted and re-hosted as Salesforce Files with the original ContentDocumentLink preserved.