Migrate from BigChange to HubSpot

Jobs have no native HubSpot equivalent — custom field architecture determines reporting depth

BigChange organizes work around Job records with fields like job_status, job_priority, scheduled_start, and actual_end. HubSpot has no native Job object — only Deals, Contacts, Companies, and (Enterprise-only) Custom Objects. We map Jobs to Deals with custom fields for every job-specific attribute. This preserves the data, but the custom field count grows quickly: a typical field service migration creates 8–15 custom Deal properties for job attributes. If you plan to report on job completion rates or technician performance in HubSpot, those custom fields need to be built before the migration runs so reports can reference them from day one.

BigChange workflows, scheduling rules, and job-type triggers do not migrate to HubSpot

BigChange workflows govern job routing, engineer assignment, alert triggers, and Schedule of Rates application. HubSpot's workflow engine operates on CRM objects — contact properties, deal stage changes, and form submissions — and has no native concept of job status transitions or engineer availability. Field-service automation logic must be rebuilt in HubSpot using workflows, sequences, or the Service Hub automation layer. We export your BigChange workflow definitions as structured JSON so your implementation team has a rebuild reference. This is the most common source of post-migration operational surprises for teams that did not plan for it.

Owner resolution by email — inactive or unprovisioned BigChange users create unassigned records

BigChange User records do not map to HubSpot Owners automatically. Resolution requires an exact email address match between the BigChange user and an active HubSpot User. If a BigChange engineer or office staff member does not have a HubSpot seat, their records route to a fallback owner or remain unassigned. We flag all unmatched owners before the migration runs and provide a resolution list so you can create HubSpot accounts or reassign before the final cutover.

BigChange Schedule of Rates and quote line item logic has no HubSpot equivalent

BigChange's Schedule of Rates defines pre-agreed pricing by job type and customer. Quote line items carry unit, rate, quantity, and tax data. HubSpot Deals do not natively store line items — the Products/Line Items object exists but behaves differently from BigChange's quote structure. Rate codes and pricing logic must be rebuilt as HubSpot Products, custom properties on Deals, or Service Hub Quote Tools. We map quote header totals and line item summaries as custom fields on the Deal, but the dynamic pricing rules that BigChange applies at quote generation time do not transfer.

Financial documents (invoices, credit notes) migrate as reference data only

BigChange generates invoices and credit notes tied to jobs, with full billing amounts, tax calculations, and document numbers. HubSpot has no native billing or accounts receivable module. Invoice records migrate as custom properties on the associated Deal — invoice number, total, and document reference — for audit and reconciliation purposes. But HubSpot cannot regenerate, reissue, or track payment status on those invoices. Your accounting integration needs to be rebuilt or replaced with a third-party tool connected to HubSpot.