Migrate from BigChange to Salesforce Sales Cloud

Job records have no native equivalent in Salesforce's standard CRM object model

BigChange Jobs are work orders with their own lifecycle semantics — job type, engineer assignment, site address, scheduled time, and custom field properties — that do not map to any standard Salesforce CRM object without custom fields. FlitStack maps Jobs to Salesforce Cases using custom fields (Engineer__c lookup, Job_Type__c pick-list, Site_Address__c text field), but the Salesforce admin must pre-create these custom fields and configure Case record types and page layouts before data lands. Without this preparation, the Job data will migrate without the site-specific context that makes it actionable.

Financial documents — invoices, credit notes, purchase orders — have no Salesforce equivalent

BigChange stores structured financial documents (invoices, credit notes, purchase orders) as records in its financial module. Salesforce Sales Cloud has no native financial document object — there is no Account-Payable or billing record type. FlitStack migrates these as Salesforce Files (ContentVersion/ContentDocument) with custom metadata fields (Document_Type__c, Document_Number__c, Amount__c) so the files are accessible on the Account record, but the financial data is not queryable in Salesforce reports and cannot participate in Salesforce's Opportunity Amount calculations. Teams needing billing reconciliation in Salesforce must rebuild this in a custom object or integrate a dedicated accounting tool.

Many-to-many engineer-to-job associations require a custom junction object

BigChange allows multiple engineers to be assigned to a single Job, and an engineer can appear across many Jobs — a many-to-many relationship that has no built-in Salesforce equivalent for the Case object. Salesforce Opportunity has OpportunityTeamMember and OpportunityContactRole, but Cases have no standard role-based junction for internal users. FlitStack creates a custom Engineer_Job_Assignment__c junction object with lookup fields to both the Case and the Contact record representing the engineer, with a Role__c pick-list field to capture the assignment type. The Salesforce admin chooses whether to create engineer Contact records or use the junction against a separate Engineer__c custom object.

Quote line items require PricebookEntry resolution before OpportunityLineItem insertion

BigChange Quote_Line_Items store product names and pricing directly without a Pricebook concept. Salesforce requires OpportunityLineItems to reference a PricebookEntry (which ties a Product2 record to a specific Pricebook2). If BigChange quotes use product names that do not match existing Salesforce Products, FlitStack either creates placeholder Product2 records during migration or flags unmatched items for admin review before insertion. This resolution step adds a pre-flight check to the Quote migration phase and must complete before OpportunityLineItem records can be loaded.

BigChange's DaaS data-retention policy limits historical data access from June 2026

BigChange's Data as a Service platform is moving to a rolling three-year data-retention window starting June 1, 2026, after which data older than three years will rotate out of the live DaaS environment. Teams with records predating January 2023 must snapshot that data independently before June 2026 or it will no longer be accessible via BigChange's DaaS API. FlitStack can incorporate an early extraction of historical data into the migration plan, but this must be requested before the retention rollover occurs.