Migrate from ServeCircle to Salesforce Sales Cloud

ServeCircle customers are a flat record combining company name, contact person, phone, and email. FlitStack splits these into a Salesforce Account (for the business entity) and a Contact (for the primary person), preserving the original customer ID as Source_System_ID__c on both records.

ServeCircle Advanced tier includes a dedicated 'Service Account' module for client records distinct from the general customer object. These map 1:1 to Salesforce Account with a custom Account_Type__c pick-list field set to 'Service Account', preserving the category distinction. Teams should filter reports on this field to separate service-account customers from standard business accounts within Salesforce reporting and list views.

Job sheets are the core ServeCircle object — they contain customer reference, technician assignment, service type, parts used, status, and timestamps. FlitStack maps job sheets to Salesforce Case so the standard Case object handles status transitions, priority, and assignment rules. The original job sheet number is stored as Source_Job_Sheet_Number__c.

Job sheets that represent billable service events with a revenue amount map to Salesforce Opportunity. The deal amount is the sum of labour and parts from the job sheet. Pipeline and stage are set to a default 'Service Revenue' record type — your team customises this to match your sales process after migration.

ServeCircle generates invoices tied to job sheets. These merge into Salesforce Order records for structured billing history. Original invoice PDFs are stored as Salesforce Files and linked to the Order. A custom Invoice_History__c object captures ServeCircle-specific fields like payment method and pending/confirmed status.

ServeCircle inventory items (parts, spares, consumables) map to Salesforce Product2. A custom Cost_Basis__c currency field on Product2 preserves the original cost price from ServeCircle, which is not a native Salesforce Product field. Each product is added to the Standard Price Book and any custom price books in use.

ServeCircle supports unlimited branches as a native attribute on every record. Salesforce has no built-in branch concept. FlitStack creates a Branch__c custom field on Account, Case, and User so every record carries its originating branch. For territory routing, Salesforce Field Service service territories can be layered on top.

ServeCircle assigns technicians to job sheets. These map to Salesforce User records matched by email. If a ServeCircle technician has no email in the system, a Salesforce User is created with a placeholder email and the original ServeCircle technician ID stored as Source_Technician_ID__c.

ServeCircle attachments on job sheets — including diagnostic photos, signed forms, and device images — are downloaded from the web interface and re-uploaded as Salesforce Files via the Bulk API. Each file is stored as a ContentVersion record and linked to the corresponding Case via ContentDocumentLink so that files appear natively in the Case's Files and Attachments related list, maintaining full context for service history and customer communication.

ServeCircle Enterprise allows custom fields on job sheets. These must be manually catalogued from the ServeCircle UI before migration. Each custom field becomes a Salesforce Case custom field with the __c suffix. Field data types are mapped as closely as possible: text → Text, number → Number, picklist → Picklist.

ServeCircle Advanced and Enterprise tiers include a reviews and feedback feature for customer satisfaction tracking. Salesforce has no native review object, so FlitStack migrates this data to a custom Review__c object linked to the parent Case via a Lookup relationship. The custom object preserves the star rating value, full feedback text, and the original submission timestamp for historical reporting and customer experience analysis after go-live.

ServeCircle Enterprise includes warranty service claims and claim accounts for franchisees. These map to Salesforce Contract for structured AMC contract tracking, with a custom Warranty_Claim__c child object capturing claim-specific fields like claim status, part replaced, labour hours, and franchisee reference ID. This parent-child structure mirrors ServeCircle's warranty hierarchy while leveraging Salesforce's native Contract object for renewal reminders and asset management integration.