Migrate from BigChange to Freshsales

BigChange Persons (customers and stakeholders) map 1:1 to Freshsales Contacts. Email, phone, and address fields map directly with no transformation required. Persons without email addresses are flagged before migration begins — Freshsales Contacts require a valid email address by default via API validation rules, so records missing email are held for manual correction or email assignment before the import runs.

BigChange Customers (business entities) map to Freshsales Accounts. Company name, industry, annual revenue, employee count, and website URL map as direct field pairs with no transformation. Multi-site customers in BigChange with multiple Persons create a primary Account with multiple linked Contacts, preserving the relationship hierarchy. Industry pick-list values are mapped per source value, with unmapped values defaulting to Freshsales Other.

BigChange Jobs are the primary operational record. We map Jobs with revenue value to Freshsales Deals, preserving the job name as Deal Name, total value as Amount, scheduled start/end as custom date fields, and job status as Deal Stage via value mapping. Jobs without monetary value are mapped as Deals with zero amount or archived as a custom Job object.

BigChange job status values (e.g., Booked, In Progress, Complete, Invoiced, Cancelled) map value-by-value to Freshsales pipeline stage names. Each BigChange pipeline maps to one Freshsales pipeline, and status values map to stage names within that pipeline. Stage probability and forecast category are re-applied on the Freshsales side.

BigChange Quotes with pricing tiers and line items map to Freshsales Products if they represent sellable items, or to a custom Quote object if the structure carries custom fields not supported by the standard Product model. Quote status (Draft, Sent, Accepted, Rejected) migrates as a custom pick-list field.

BigChange custom properties defined via DaaS quote_custom_fields and job-type custom fields are mapped to Freshsales custom fields on Contact, Account, Deal, or custom objects. Field types are matched (text to text, number to number, date to date) and pick-list values are mapped value-by-value before migration runs.

BigChange Asset Register has no native Freshsales equivalent. We create a custom Asset object with fields for asset name, serial number, linked Account lookup, maintenance history, and site location. The asset-to-customer link migrates as an Account lookup field on the custom object.

BigChange users are matched to Freshsales users by email address. Unmatched users are flagged before migration — your team either provisions the user in Freshsales first or reassigns their BigChange records to an existing Freshsales user before the import runs. Owner resolution is critical for accountability tracking after migration, so this step is verified during the sample migration phase.

Files attached to BigChange Jobs — including photos, PDFs, worksheets, and site photos — are downloaded and re-uploaded to Freshsales as Files linked to the corresponding Deal record. File size limits vary by Freshsales plan tier and are observed during upload; files exceeding the limit are flagged for manual retrieval from BigChange after migration.

BigChange job notes and internal comments migrate as Freshsales Sales Activities of type Note. Original timestamps and the linked user (matched by email) are preserved during migration. Notes linked to a specific Person or Job carry the corresponding Contact or Deal association in Freshsales, maintaining the full audit trail for customer interactions.