Migrate from Swivl Tech to Freshsales

Swivl Tech customers are person-level records with associated business information. We map the person fields to Freshsales Contact and create a corresponding Account record using the customer's business name. The Contact gets linked to the Account via the AccountId lookup field.

Swivl Tech customers entered with a business name only (no individual contact) map directly to Freshsales Account records. The business name populates the Account Name field. A primary contact is created manually or from any individual associated in Swivl Tech.

Swivl Tech stores site addresses on customers or job records. We map the primary site address to the Account's billing address fields in Freshsales. Additional site addresses are preserved as custom address fields or as separate Account records when multiple locations per customer are detected.

Each Swivl Tech job record maps to a Freshsales Deal. The job name becomes the Deal name, the job total amount becomes the Deal amount, and the job status maps to the appropriate Freshsales pipeline stage. The Deal is linked to the Account and Contact from the customer mapping.

Swivl Tech job status values (e.g., Scheduled, In Progress, Completed, Cancelled) map to Freshsales pipeline stage names via a value-by-value mapping. The mapping is configured per pipeline — multiple Swivl Tech pipelines each get their own Freshsales pipeline with stage value translation.

Swivl Tech job types (e.g., Plumbing, Electrical, HVAC) have no direct Freshsales equivalent. We create a custom pick-list field (Job_Type__c) on the Deal object and map each Swivl Tech job type value to the corresponding pick-list entry. This preserves the service category distinction across both systems and allows Freshsales reports to filter by job type once the migration is complete.

Swivl Tech estimates with line items translate to Freshsales Deals with associated Products. Each estimate line item becomes a Deal Product entry linked to the Deal. If the estimate includes custom pricing rules, we map it to a custom object for reference until CPQ is configured.

Freshsales has no native invoicing object. Swivl Tech invoices are migrated as a custom object (Invoice__c) linked to the parent Deal and Account, storing invoice number, amount, status, and date. If the destination is Freshsales Suite, invoices can alternatively live in the billing module.

Swivl Tech invoice line items and job costing data do not map to any standard Freshsales object. We create a custom object (Invoice_Line_Item__c) linked to Invoice__c and the parent Account, preserving description, quantity, unit price, and total cost. This ensures financial detail from Swivl Tech is not lost and remains accessible for reference and audit purposes in Freshsales.

Swivl Tech technician assignments on jobs map to Freshsales User records. We resolve technicians by email match against Freshsales users. Unmatched technicians are flagged before migration — the team either creates Freshsales users first or assigns those records to a fallback owner.

Swivl Tech photos and documents attached to job records are downloaded and re-uploaded to Freshsales Files, linked to the corresponding Deal record. File size limits apply per Freshsales plan. Inline images in notes are extracted and hosted as Freshsales attachments.

Any Swivl Tech custom properties on customers, jobs, or estimates are migrated to Freshsales custom fields. Freshsales supports custom fields on Contact, Account, and Deal objects. The custom field data type is inferred from the source value type — text maps to text, numbers to number, dates to date.