Migrate from The Service Program to Salesforce Sales Cloud

The Service Program's customer record maps directly to Salesforce Account. Company name becomes Account.Name, phone maps to Phone, and address fields map to Account.BillingAddress or ShippingAddress. QuickBooks customer type can populate a custom Industry or Type field on Account. If the customer has multiple contacts, each contact is linked to the Account via a Contact record with the AccountId field set accordingly.

Named contacts stored under each customer map to Salesforce Contact with AccountId pointing to the parent Account. The primary contact flag from The Service Program maps to Contact.IsPrimary on AccountContactRelation. Email, phone, and job title transfer as standard fields. If a contact lacks an email address, FlitStack flags the record for manual review and can optionally create a placeholder email to preserve the relationship in Salesforce.

The Service Program tracks multiple service addresses per customer. Without a Salesforce-native equivalent, FlitStack creates a Service_Location__c custom object with AccountId lookup, address fields, and location-type pick-list. Each service location from The Service Program becomes a separate record linked to the parent Account.

Work orders in The Service Program map to Salesforce Case. Work order status (Open, In Progress, Closed) maps to Case.Status via value mapping. The service-address link on the work order becomes Case.AccountId via the Service_Location__c record. Case.Origin can be set from the work order source channel.

Line items on a work order (parts, labor tasks, services performed) are written as CaseComments for audit history, or as a custom Work_Order_Line__c child object if your Salesforce edition supports it and the volume warrants a separate object. FlitStack surfaces the choice in the migration plan.

The Service Program technician records are mapped to Salesforce Users by email match. If a technician has no email in The Service Program, they are flagged for manual User creation before migration. Technicians without Salesforce User accounts become Case.CreatedBy fallback or a custom Technician__c field on Case.

The technician assigned to a work order in The Service Program becomes Case.OwnerId in Salesforce, resolved against the matched Salesforce User. Unresolved assignments default to a service-queue Case.QueueId configured before migration. The service queue is set up with appropriate sharing rules so that any cases assigned to it are visible to dispatch managers without giving each technician a full Salesforce license. Queue-based assignment also simplifies audit trails and reassignment workflows.

Appointment date and time from The Service Program's calendar scheduling maps to a Salesforce Event (with WhoId=Contact, WhatId=Case) for full calendar visibility, or to custom Scheduled_Date__c and Scheduled_End__c datetime fields on Case for quick reporting. Your admin chooses based on calendar dependency.

The Service Program does not store invoices independently — they live in QuickBooks. Invoice and payment history is preserved by linking to the QuickBooks record ID as a custom External_Reference__c field on Account. Salesforce Opportunities can be created for revenue tracking if you need a pipeline view of service contracts.

The Service Program's dispatch grouping and route assignments have no Salesforce native equivalent. FlitStack creates a Dispatch_Route__c custom object or uses a Salesforce Group for technician team routing, with a route reference stored on the Case record. Workflow rules for auto-assignment must be rebuilt in Salesforce Flow.

Notes attached to work orders in The Service Program migrate as Salesforce CaseComments or FeedItem entries. File attachments re-upload to Salesforce Files (ContentDocument / ContentVersion). Original timestamps and creating technician are preserved in the audit metadata. During migration, FlitStack maps the original file path to a ContentDocumentLink that attaches the file to the relevant Case, ensuring technicians can access the original attachments without re-uploading manually.