Migrate from Service In Sync to Zoho CRM

Service In Sync client records map directly to Zoho CRM Contacts. The client name splits into First Name and Last Name. Email, phone, and address fields map 1:1. Service In Sync client records without a linked company land as Contacts with no AccountId — your Zoho admin sets a default Account or creates one manually.

Service In Sync company records map to Zoho CRM Accounts. Company name maps to Account Name, domain maps to Website, industry maps to Industry pick-list (value-by-value mapping), and employee count maps to Number of Employees. Parent-company hierarchies map to the Parent Account lookup in Zoho if the source data includes them.

Service In Sync clients that are individual consumers rather than business contacts map to Zoho CRM Leads. Split is based on whether the company_name field is populated. Records with a populated company map to Account; records without map to Lead. The Lead Status field defaults to 'Not Contacted' and can be updated in Zoho after migration.

Service In Sync quotes and estimates map to Zoho CRM Deals. The quote total maps to Deal Amount, the quote name maps to Deal Name, and the quote status (Open, Won, Lost) maps to Zoho Stage pick-list values via value-by-value mapping. Service In Sync quote line items require a Zoho Products module to be set up first so they can be linked as Products on the Deal.

Service In Sync line items on quotes do not map to a standalone Zoho object. They require a Zoho Products module with product name, unit price, and quantity. FlitStack creates the Products module entry and links each line item to the corresponding Deal as a Deal Product record. If no Products module exists, line items are stored as custom fields on the Deal record.

Service In Sync job records and scheduling blocks map to Zoho CRM Tasks. The job description maps to Task Subject, the scheduled date maps to the Task due date (DUE_DATE field), and the assigned technician email resolves to a Zoho User as Task owner. Job status (Pending, In Progress, Completed) maps to Task Status pick-list values via value mapping.

Service In Sync payment records (deposits, amounts paid, payment status) have no native Zoho CRM equivalent. FlitStack preserves payment data as a custom field set on the Deal record (Payment_Status__c, Amount_Paid__c, Deposit__c) and attaches payment transaction records as Notes on the Deal for audit trail continuity.

Service In Sync's review-request logic (automated follow-up after service completion) has no Zoho CRM equivalent. The review-request history is preserved as a Note attached to the Contact record. Zoho's Survey integration and review-request workflows must be rebuilt using Zoho Survey or Zoho CRM's workflow rules post-migration.

Service In Sync custom fields on client records (e.g., service_type, contract_status, technician_rating) require Zoho CRM custom field creation. FlitStack reads the Service In Sync field schema and creates matching custom fields in Zoho's Contacts module via the Zoho CRM Fields API (POST /settings/fields?module=Contacts). Field type mapping: text → varchar, number → integer, date → date, picklist → picklist with values preserved.

Service In Sync custom fields on job records (e.g., job_category, priority_flag, site_address) migrate as custom fields on the corresponding Zoho Task record. If the Zoho Contacts module already has custom fields, the same naming convention and field type mapping applies. Zoho's 300-field-per-module limit applies to the sum of standard and custom fields.

Service In Sync file attachments on client records, quotes, and jobs re-upload to Zoho CRM's Attachments API. Each attachment is associated with the target Zoho record (Contact, Account, or Deal) via the related_record_id. Zoho's file size limit is 10 MB per attachment for standard imports; larger files may require a different handling approach.

Service In Sync user IDs and technician assignments resolve by email match against Zoho CRM Users. Unmatched owners are flagged before migration and assigned to a fallback Zoho User designated by your admin. No record lands in Zoho without a valid OwnerId. This step must complete before any record write to avoid orphaned owner references.