Migrate from ServeCircle to HubSpot

ServeCircle customers and service accounts map to HubSpot contacts with a linked HubSpot company record. The primary branch affiliation from ServeCircle is preserved as a custom pick-list property on the contact. If a customer has multiple service accounts across branches, all accounts link to the same HubSpot contact via association.

ServeCircle job sheets — the core service record — map to HubSpot tickets with a custom pipeline. The job-sheet status (Open, In Progress, On Hold, Completed, Cancelled) becomes a HubSpot ticket pipeline stage. Custom fields on the job sheet (technician assigned, service type, parts used, signature captured) map to custom ticket properties with type preservation.

ServeCircle quotations map to HubSpot deals with a custom boolean property Quotation_Is_Quotation__c set to true, separating them from pipeline-based sales deals. The quotation amount maps to the deal amount field. Approval status from ServeCircle (Pending Approval, Approved, Rejected) maps to a custom pick-list field on the deal so the approval state is visible in HubSpot reporting.

ServeCircle invoice records (amount, payment status, payment date, currency) are preserved as deal line items attached to the corresponding HubSpot deal. Payment status (Pending, Paid, Overdue) maps to a custom pick-list on the deal. Original invoice number is stored as an immutable custom property on the deal for audit traceability. Multi-currency invoices record the original currency code alongside the converted amount.

ServeCircle inventory items with a product type (parts, accessories, packaged service items) map directly to HubSpot products using the product name as the HubSpot product name, SKU as the HubSpot product code, and unit price as the sales price. Physical inventory quantities are stored as a custom number property Quantity_On_Hand__c — HubSpot does not track live stock levels natively.

Each ServeCircle branch maps to a HubSpot team for access control and data visibility scoping. Branch-level job-sheet pipelines can map to separate HubSpot ticket pipelines, or all branches share a single pipeline with a Branch__c custom property for filtering. FlitStack delivers the branch-to-team mapping plan as part of the pre-migration schema setup document.

ServeCircle quotation line items map to HubSpot deal line items, preserving product reference, quantity, unit price, discount, and line-total. Line items are attached to the corresponding quotation deal in HubSpot. If a line references a ServeCircle inventory item that is not yet a HubSpot product, FlitStack creates the HubSpot product record first before attaching the line item.

ServeCircle attachments on job sheets and invoices (signatures, images, documents) are downloaded and re-uploaded to HubSpot Files. The HubSpot file URL is stored on the corresponding ticket or deal record in a custom URL property. ServeCircle lists Attachments as 'Coming soon' — any existing attachments are migrated if present; FlitStack surfaces any empty attachment fields as a migration-gap item for manual handling.

ServeCircle service categories (mobile repair, computer repair, on-site service, pickup service) map to a HubSpot custom pick-list property on the ticket object named Service_Category__c. Value-by-value mapping preserves the exact category labels from ServeCircle. This pick-list is used to filter ticket views and drive workflow routing in HubSpot.

ServeCircle technician records are created as HubSpot contacts in a separate 'Technicians' list with a custom Internal_Technician__c boolean set to true. They are not HubSpot users — only contacts. Ticket assignment maps the ServeCircle assigned-technician field to a custom contact reference property on the HubSpot ticket. If the technician should become a HubSpot user (e.g., for service-hub reporting), the team creates HubSpot user accounts before migration.

ServeCircle's review and feedback module (Advanced and Enterprise tier) captures post-service ratings and comments. HubSpot has no native review object — the data migrates as a custom object (Service_Feedback__c) with rating (number), comment (text), and submitted_at (datetime) fields attached to the originating ticket record. Feedback is preserved for reporting but does not trigger HubSpot-native NPS workflows without manual rebuild.

ServeCircle's SMS and email alert configuration (Premium Sales tier) sends status notifications to customers on job registration, progress, and completion. HubSpot has no equivalent notification engine for service tickets — this logic must be rebuilt in HubSpot using Workflows with enrollment criteria based on ticket stage changes. FlitStack exports the ServeCircle alert configuration as a reference document for the HubSpot admin to use during workflow rebuild.