Migrate from Service In Sync to HighLevel

Service In Sync contacts map directly to HighLevel contacts. Primary company association migrates as the primary CompanyId lookup. Contacts without a company receive a placeholder company record or land unassigned until manually linked in HighLevel. All original contact IDs are preserved in a custom field to maintain cross-reference integrity.

Service In Sync companies map to HighLevel companies. Parent-company hierarchies (if present) migrate as HighLevel Parent CompanyId. Multi-address companies collapse to the primary address field, with additional addresses preserved as custom fields. Company phone numbers and website URLs are transferred directly to the corresponding HighLevel company fields.

Service In Sync jobs are the primary work record and translate to HighLevel opportunities. The job name becomes the opportunity name, the estimated or final amount becomes the opportunity value, and the job status maps to a HighLevel pipeline stage. Multiple service types within one job require stage-split logic.

Service In Sync job statuses (Scheduled, En Route, In Progress, On Hold, Completed, Cancelled) map to HighLevel pipeline stages. The mapping requires creating a HighLevel pipeline that mirrors the job lifecycle, with probability weights applied per stage. Cancelled and On Hold statuses may require custom stage creation.

Service In Sync estimates attach to jobs and include line items, approval status, and deposit amounts. These merge into the target HighLevel opportunity as custom fields (Estimate_Amount__c, Approval_Status__c, Deposit_Collected__c). Line items become a JSON blob or separate custom object depending on volume.

Service In Sync appointments with date, time, duration, assigned technician, and location map to HighLevel appointments. HighLevel's calendar integration supports availability checks and booking links post-migration. The original appointment status (confirmed, rescheduled, no-show) preserves as a custom field, and any recurring appointment patterns are captured for future scheduling.

Service In Sync payment records (amount, method, date, reference) do not have a native HighLevel equivalent. Partial payments attach to the related opportunity as Paid_Amount__c and payment notes, with full payment history preserved in a custom object or note for reconciliation. HighLevel's payments integration handles future transactions post-migration.

Service In Sync's automated review-booster triggers don't transfer. The review request history (which customers were asked, when, on which platform) migrates as custom fields on the contact record (Review_Requested__c, Review_Platform__c). HighLevel's reputation management handles future review requests, and all historical request timestamps are preserved in a custom date field for audit purposes.

Service In Sync custom fields on jobs (e.g., equipment type, service tier, warranty flag) create as HighLevel custom fields on the opportunity object. Field types map to nearest HighLevel equivalents: text fields, pick-lists, dates, and checkboxes each have a direct HighLevel counterpart. Numeric fields requiring calculations may need formula field alternatives.

Service In Sync custom fields on contacts (e.g., preferred technician, service preferences, contract tier) create as HighLevel contact custom fields. Multi-select pick-lists from Service In Sync map to HighLevel multi-select or tag fields. Unique constraint fields (e.g., license numbers) map to HighLevel single-line text with uniqueness validation if needed.

Service In Sync staff and technicians map to HighLevel users by email match. Owner assignment on jobs migrates as the Opportunity OwnerId in HighLevel. Unmatched staff members are flagged before migration; invite them to HighLevel or assign to a fallback user.

Service In Sync file attachments on jobs and contacts re-upload to HighLevel. File size limits (HighLevel default 25MB per file) apply. Inline images in notes are extracted and rehosted. Documents attached to estimates download and re-upload as opportunity attachments, and each file retains its original creation timestamp for traceability.