Migrate from BigChange to Nutshell

BigChange Persons map directly to Nutshell People. The Person record is the primary customer entity in both systems — name, email, phone, address, and company association transfer 1:1. Owner resolution happens by email match against existing Nutshell users; unresolved owners are flagged before migration commits.

BigChange Companies map to Nutshell Companies with all standard fields including name, website, address, industry classification, employee count, and annual revenue transferred directly. Parent-company hierarchies present in BigChange map to Nutshell's parent company lookup field if that feature is configured in your Nutshell account; otherwise the structure is preserved as a flat list without hierarchical relationships.

Jobs translate to Nutshell Deals to preserve service history as a sales record. Job status (e.g., Pending, In Progress, Completed, Invoiced) maps to Nutshell Deal stage values; the stage pick-list is configured per your Nutshell pipeline setup. Job financial totals (labour, parts, expenses) map to Deal monetary fields where applicable.

BigChange custom fields on Jobs require pre-creation in Nutshell as Deal custom fields before migration runs. Each custom field type (text, number, date, pick-list) maps to the equivalent Nutshell field type. We provide a field creation checklist based on the BigChange schema export so your Nutshell admin can pre-build the fields.

BigChange Quotes split across Nutshell: line items and pricing may land as Deal fields or a custom Quote object depending on whether the quote has been accepted. Accepted quotes that have converted to Jobs migrate as Deals with a closed-won stage; draft quotes migrate as Deals in an early stage with quote reference preserved as a custom field.

BigChange custom fields on Persons (e.g., trade licence number, certification expiry, preferred engineer) must be created in Nutshell as Person custom fields before migration. We export the full BigChange custom field schema and generate a field-creation guide so Nutshell-side setup completes before data loads.

BigChange custom fields on Companies (e.g., site access requirements, VAT number, contract tier) require equivalent custom fields in Nutshell Companies. The same pre-migration field creation workflow applies: we provide a schema diff and your Nutshell admin creates the fields before migration executes.

BigChange Engineers and Resources are staff records tied to job assignments. In Nutshell, engineers are regular Users (for licensing purposes) with job-assignment data stored as custom fields on the related Deal rather than as a native object. We preserve engineer-to-job links as custom Deal fields.

BigChange file attachments on Jobs, Persons, or Companies re-upload to Nutshell as Files linked to the corresponding Person, Company, or Deal record. File size limits apply per Nutshell's upload constraints. Inline images in notes are downloaded and re-hosted as Nutshell file attachments.

BigChange job-related notes, calls logged, and email threads linked to a Job migrate as Nutshell Tasks and Notes attached to the corresponding Deal. Original timestamps and the engineer or staff member who created the activity are preserved as Task fields (owner, created date).

BigChange workflow rules (job alerts, status notifications, automated job-card generation) have no equivalent in Nutshell's data model. These must be rebuilt in Nutshell using Nutshell's automation features post-migration. We provide a workflow audit export from BigChange as a reference document for your Nutshell admin.

BigChange vehicle tracking and GPS data is a hardware-dependent feature with no CRM equivalent in Nutshell. Travel history, route data, and vehicle telemetry do not migrate. This data lives in BigChange's tracking infrastructure and remains in the source system. Organizations requiring this data should export it to a dedicated fleet management solution or data archive before migration completes.