Migrate from The Customer Factor to Nutshell

The Customer Factor's unified customer record maps to Nutshell Person for individual contacts. We extract name, email, phone, and address fields and write them to the Nutshell Person object. The account-company relationship is resolved separately via the Nutshell Account object.

The Customer Factor stores company data inside the customer record alongside contact information. We extract company name, domain, industry, and address into Nutshell Account, then link the Account to the corresponding Person record via the accountId field on Person. This creates the relational structure Nutshell expects for person-account relationships.

The Customer Factor prospect records map directly to Nutshell Lead objects. Fields including name, company, phone, email, and any custom fields transfer as-is. Prospect status values map to Nutshell Lead status pick-list values via value-mapping, ensuring status continuity across both systems.

Jobs represent scheduled service work in The Customer Factor with fields for type, status, assigned technician, and scheduled date. Since Nutshell has no job object, we transform jobs into Activity records (type = 'Job') and write job-type, status, and scheduling details into the Activity description or custom fields.

Jobs tied to revenue-generating work can also map to a Nutshell Opportunity with job details (type, status, date) stored in custom fields on the Opportunity. This preserves job-to-revenue context for pipeline reporting in Nutshell and keeps the financial relationship visible in your sales pipeline view.

The Customer Factor estimate records have no native Nutshell equivalent — Nutshell has no estimate object. We map estimate number, status, and line-item summary to Opportunity custom fields (Estimate_Number__c, Estimate_Status__c) and write the line items as plain text in the Opportunity description field.

Nutshell has no native invoicing capability. Invoice records cannot be represented natively. We create a reference Activity record in Nutshell with invoice number and status, and export the full invoice dataset as a CSV for use with external accounting or billing tools.

The Customer Factor user accounts map to Nutshell users by email address match. We flag any owner in The Customer Factor without a corresponding Nutshell user account before migration so you can invite them or assign records to a fallback owner.

The Customer Factor custom fields on customers become Nutshell custom fields on the Person object. We create each custom field in Nutshell via the Settings > Fields interface before import, preserving data type (text, date, pick-list) as closely as Nutshell allows.

The Customer Factor custom fields on prospects translate to Nutshell Lead custom fields. All custom field definitions are documented in the pre-migration schema plan, where each field's type and pick-list values are mapped. The fields are then created in Nutshell before the import step runs.

Files attached to The Customer Factor customer or job records are downloaded and re-uploaded as file attachments to the corresponding Nutshell Person, Account, or Activity record. File size limits apply per Nutshell's upload constraints, and the attachment relationships are preserved during the migration.