Migrate from Swivl Tech to Zoho CRM

Swivl contacts with client type map directly to Zoho Contacts. Email, phone, address, and company lookup (Client) transfer 1:1. OwnerId resolves by matching Swivl owner email to a Zoho user — unmatched owners flagged before migration runs so records do not land without a valid owner.

Swivl companies map to Zoho Accounts using Account Name, website domain, industry, employee count, and annual revenue. Swivl's multi-location flag becomes a Zoho custom field since Zoho Accounts support a single billing address per record — additional addresses migrate as custom multi-line text.

Swivl Job is the primary work-order object and has no direct Zoho CRM equivalent. Jobs migrate to Zoho Tasks with the Subject set to the job name, Description carrying the full job notes, and a custom field SWIVL_Job_ID__c storing the source Swivl job ID for traceability. Task status and priority derive from Swivl job status and priority values via value mapping.

Swivl job records store service type, materials used, and custom measurement data as structured custom properties. These map to Zoho custom fields on the Task module — SWIVL_Service_Type__c, SWIVL_Materials__c, and SWIVL_Custom_Measurements__c must be pre-created in Zoho before the migration batch runs. We deliver a custom-field creation checklist as part of the migration plan.

Swivl job line items (materials, quantities, unit prices) are structured rows attached to a job. Zoho CRM Tasks do not support native line items. We merge line-item data into a single SWIVL_Line_Items__c multi-line text field formatted as name|qty|unit_price|total per row, preserving all material data for reference without requiring a custom module.

Swivl technicians are assigned as job owners. Zoho CRM OwnerId must reference an active Zoho user. We resolve each technician by email match — if no matching Zoho user exists, we flag the record and assign it to a fallback owner specified by your admin. Pre-inviting Swivl technicians to Zoho before migration eliminates orphaned records.

Swivl job notes attach as free-text records to a job. These migrate as Zoho Notes associated with the corresponding Task using the SWIVL_Job_ID__c reference. Original create timestamps and note authors preserve the full audit trail on the Zoho task, ensuring continuity of service history documentation and accountability records across the migration.

Swivl invoices are financial documents tied to completed jobs. Zoho CRM does not store invoice records — those live in Zoho Books or a third-party accounting tool. We preserve Swivl invoice numbers, amounts, and dates as read-only custom fields on the migrated Task (SWIVL_Invoice_Number__c, SWIVL_Invoice_Amount__c) for reconciliation reference before your team closes the books in Swivl.

Swivl file attachments on jobs (photos, signed forms, measurements) re-upload to Zoho as Task attachments. Zoho CRM supports up to 25MB per file. We download all job attachments from Swivl, re-upload to the corresponding Zoho Task, and preserve the original filename and upload date as attachment metadata.

Swivl's flat-rate billing tier (Free, Growth, Scale Pro) has no Zoho CRM equivalent — Zoho pricing is per-user per-month and operates independently. We store the source Swivl pricing plan as SWIVL_Pricing_Tier__c on Contact for billing audit purposes, but this field is informational only.

Swivl records technician calls and visit logs as activities on a job. These migrate to Zoho Tasks with Type='Call' or Type='Task' linked to the corresponding job Task via the SWIVL_Job_ID__c lookup. Original activity timestamps and duration data transfer to Zoho Task fields for service audit continuity.

Swivl links a Contact to a Company (client) record. In Zoho CRM, Contact has a lookup field to Account (Account_Id). We migrate the association by resolving the Swivl client company name to the newly created Zoho Account ID before writing Contact records, ensuring every contact lands linked to the correct account.