Migrate from Service In Sync to Freshsales

Service In Sync Clients map to Freshsales Accounts as the primary business entity. The client's business name, address, website, and industry fields map to Freshsales Account fields. Clients with no company name (individual clients) create a Freshsales Account using the client name and are flagged for manual review.

Service In Sync Contact records map to Freshsales Contacts, preserving first name, last name, email, phone, mobile phone, job title, and address fields. The Contact's primary Client is stored as the Freshsales AccountId lookup. Multiple contacts per client are preserved as individual Freshsales Contact records linked to the same Account.

Service In Sync Clients without an active job or invoice may represent prospective customers rather than established accounts. We flag these records for review and offer to route them as Freshsales Leads using the client's company name, contact email, and any source-tag as the lead's initial data. The split rule is configurable per migration — default is any Client with zero Jobs and zero Invoices routes to Lead.

Service In Sync Jobs without a linked Estimate or with an Estimate amount below the opportunity threshold (configurable, default $0) map to Freshsales Tasks. Task Subject uses the job name or job type, Description stores the job description and service notes, and the original Job status (Scheduled, In Progress, Completed, Cancelled) maps to a custom Job_Status__c pick-list field. Original technician assignments are resolved by email match to Freshsales users.

Service In Sync Jobs that have an active Estimate with a positive amount map to Freshsales Opportunities. The Opportunity Name uses the Estimate name or Job name, Amount uses the Estimate total, Close Date uses the Estimate expiry date, and Pipeline/Stage are set from the migration configuration. Line items from the Estimate are stored as Opportunity Products if the Freshsales plan includes the Products module; otherwise they are preserved in a custom field as JSON.

Service In Sync Appointments map to Freshsales Events, preserving the original start time, end time, timezone, subject, and assigned technician (mapped to Freshsales Owner by email). Recurring appointments generate individual Freshsales Event records for each occurrence if the count is below 50; above that threshold they are summarized as a custom recurrence note on the first Event record.

Freshsales has no native invoice object. Service In Sync Invoices migrate to a custom Invoice__c object (created in the target Freshsales account) with fields for invoice number, amount, balance due, status, due date, and linked Account/Contact lookups. If the target Freshsales plan does not support custom modules, invoice data is stored as a JSON blob on the associated Opportunity or Account record.

Service In Sync's review-generation feature creates customer reviews on external platforms. The review invitation records, status (Invited, Submitted, Pending), and rating are preserved as custom fields on the related Freshsales Contact record (Review_Invite_Status__c, Review_Rating__c, Review_Submission_Date__c). The actual review content is stored as a note attached to the Contact.

Service In Sync Payment records migrate as custom fields on the related Invoice__c record (if custom objects are available) or as JSON in a Payment_History__c text area field. Payment amount, payment date, payment method, and payment status (Paid, Partial, Overdue) are preserved. Freshsales does not have a native payment object — payment reconciliation reporting requires a custom report type if the custom Invoice object is used.

Service In Sync Users and Technicians are resolved against Freshsales Users by email address match. Unmatched users are flagged before migration — teams either invite them to Freshsales first or assign their records to a designated fallback owner. User role and permissions in Service In Sync do not map to Freshsales profiles; those must be reconfigured in Freshsales Settings post-migration.

Service In Sync custom fields on any object migrate to Freshsales custom fields (on the equivalent object). Custom field types map to Freshsales field types where possible: text to text, number to number, date to date. Drop-down values are mapped value-by-value if Freshsales pick-list options exist; otherwise a new pick-list is created in Freshsales using the source values.

File attachments on Service In Sync Jobs, Estimates, Invoices, or Contacts are downloaded and re-uploaded to Freshsales as Files attached to the corresponding record. File size limits apply — Freshsales caps file uploads at 25MB per file. Inline images embedded in notes are extracted and stored as separate File attachments linked to the parent record.