Migrate from Service In Sync to Salesforce Sales Cloud

Service In Sync clients with company names map to Salesforce Account records. Clients that store named individuals (first name, last name, email) also generate Salesforce Contact records linked to the Account via AccountId. If a client record lacks a last name but has a company name, it lands as Account only.

Contact-level communication fields (email, phone, mobile, and physical address) map directly to Salesforce Contact fields. Multiple phone numbers on a Service In Sync client distribute across Phone, MobilePhone, and HomePhone based on field label matching. Email addresses validate against Salesforce email format during migration; invalid emails are flagged for manual correction. Physical addresses split across MailingStreet, MailingCity, MailingState, and MailingPostalCode using comma or line-break delimiters detected in the source data.

Service In Sync jobs become Salesforce Opportunities with a dedicated Service Jobs record type. The Opportunity Name defaults to the job description or job number. Amount is populated from job total revenue if present. CloseDate is set from the job completion date or estimated finish date. RecordTypeId is set to the service record type during migration.

Service In Sync job statuses (e.g., Scheduled, In Progress, Completed, Cancelled) map to Salesforce Opportunity StageName values via a value-by-value mapping table. Where no exact Salesforce stage matches, a custom Opportunity_Job_Status__c pick-list field preserves the original status label. Probability values are re-applied based on your Salesforce Sales Process defaults.

Each line item on a Service In Sync job (labor hours, materials, equipment) maps to an OpportunityLineItem on the Salesforce Opportunity. If Service In Sync has a product catalog, those items become PricebookEntry records in the designated Pricebook. Job-level flat fees without line items become Opportunity.Amount directly. Pricebook alignment is confirmed before the full migration runs.

Service In Sync estimates migrate as Salesforce Quote records linked to the corresponding Opportunity (via OpportunityId). QuoteLineItems map from Service In Sync estimate line items using PricebookEntry. Quote status (Draft, Sent, Accepted, Rejected) is mapped from the estimate status field. If your Salesforce org does not have Quotes enabled, estimates migrate as Opportunity notes with a custom Estimate__c flag.

Service In Sync scheduled appointments with a start and end time map to Salesforce Events (Subject, StartDateTime, EndDateTime, Location). Appointments stored as date-only or all-day items map to Tasks with IsAllDayEvent=True and ActivityDate set. Assigned technician or staff member is resolved by email match to Salesforce users and set as the Task or Event OwnerId.

Service In Sync reminders and automated follow-up triggers have no native Salesforce equivalent — they are process logic, not data. FlitStack exports the list of active reminders and trigger conditions as a reference document for your Salesforce admin to rebuild in Flow. This is disclosed upfront before migration planning begins.

Service In Sync invoices map to Salesforce Order records when the org has Order Management enabled. Payment status, payment method, and amount paid map to custom fields on Order (Payment_Status__c, Payment_Method__c, Amount_Paid__c). If Order Management is not enabled, invoices migrate as a custom Invoice__c object with all line item and payment data preserved as fields.

Service In Sync's review booster and rating data has no native Salesforce equivalent. Numeric ratings (1–5 stars) migrate to a custom Number field (Rating_Stars__c) on Account. Count of reviews migrates to Review_Count__c. Full review text, if stored, migrates to a Long Text Area field (Latest_Review__c) on Account for reference.

Service In Sync custom fields on jobs and clients require Salesforce custom field creation before migration. FlitStack inventories all custom fields during the discovery phase, creates the corresponding custom fields in the target org with appropriate data types (Text, Number, Picklist, Date, Checkbox), and writes type-aware transformation rules. Custom fields are named using Service In Sync's label converted to Salesforce API naming conventions.

File attachments on Service In Sync jobs and clients are downloaded and re-uploaded as Salesforce Files (ContentVersion linked to the target object via ContentDocumentLink). File size limits apply: Salesforce caps individual file uploads at 25MB by default. Files over this limit are flagged for manual review before the full migration commits.

Service In Sync job owners and assigned technicians are resolved by email match against Salesforce users. Unmatched owners are flagged before migration runs — your team either provisions a Salesforce user account or assigns those records to a designated fallback owner. No Opportunity lands without a valid Salesforce OwnerId.

The original Service In Sync record ID is stored on every migrated record as a custom text field (Source_System_ID__c). This enables delta-run de-duplication (if a record is modified in Service In Sync during the cutover window), cross-referencing for audit purposes, and reconciliation reports between the source and destination record counts.