Migrate from Leadforce CRM to Nutshell

Leadforce Leads map to Nutshell People. Standard fields (name, email, phone, source, status) migrate directly. Company name embedded in the Lead record maps to the Nutshell Company lookup, which we resolve by either matching against an existing Nutshell Company record (by domain or name) or creating a new Company record first and then linking it. If the Lead contains only a company name with no separate Company record in Leadforce, we normalize it into the Nutshell Companies object before the Person import so the relationship is satisfied at insert time.

Leadforce Deals map directly to Nutshell Deals with monetary value, stage, and owner preserved. The Leadforce deal stage names map to Nutshell pipeline stages; we verify stage count compatibility during discovery. Owner assignment resolves by email matching against Nutshell Users. Closed-lost and closed-won stage values migrate with the original timestamps preserved.

Leadforce Activity records (calls, emails, meetings, tasks) map to Nutshell Activities with type, timestamp, owner, and linked record preserved. Activity chronology ordering is maintained by setting the Nutshell Activity date to the original Leadforce timestamp. Activity type differentiation (call versus email) migrates as a category or tag field in Nutshell depending on the destination's available field types.

Leadforce Notes attached to Leads or Deals migrate as Nutshell Notes linked to the corresponding Person, Company, or Deal record. Creation timestamps and author attribution transfer where visible in the Leadforce export. Plain-text and rich-text formats map to Nutshell's note body field.

Leadforce Attachments linked to Deals or Leads require extraction from the exported files, mapping to the corresponding Nutshell record by name or ID, and manual re-upload. We flag the attachment list during discovery, extract files from the Leadforce export bundle, and produce a mapping spreadsheet linking each file to its target Nutshell record. The actual re-upload is performed in Nutshell's interface or via API after the data layer is confirmed.

Leadforce Proposals generated from Deals contain line items and pricing. We export proposals as structured data and reconstruct them in Nutshell as Deal-associated notes containing the line item detail, or as Deal custom fields capturing total proposal value and status. Nutshell does not have a native Proposal object at the Foundation tier; if the customer requires full quote management, we document this gap and recommend a Nutshell-native quoting tool or a rebuild in Nutshell's workflow tools post-migration.

Leadforce Invoice records linked to Deals migrate as Deal-level financial metadata (total invoice amount, payment status, invoice date). We preserve payment status as a Deal field or custom field in Nutshell. Full invoice document re-creation is handled separately from the data migration via the file re-upload process.

Leadforce does not always use a separate Companies object; company data lives within Lead records as a company name field. We extract all distinct company name values from Leadforce Leads, deduplicate them, and bulk-create Nutshell Company records before importing People. The People import then resolves the Company lookup by name match. This N:1 merge is executed as a separate pre-phase to satisfy referential integrity before the Person insert runs.

Leadforce pipeline stage names and order are mapped to Nutshell pipeline stages during configuration. We verify stage count compatibility between the two platforms and configure Nutshell pipeline stages to match the Leadforce stage labels. Stage probability values from Leadforce are noted but may not map directly if Nutshell's stage probability model differs; we document any gaps for the customer admin to set in Nutshell's pipeline settings.

Leadforce Owner and user assignment maps to Nutshell Users by email match. We extract all distinct owner email addresses from Leads, Deals, Activities, and Notes, and match against Nutshell User records. Any Leadforce owner without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before the record import phase continues.

Leadforce custom fields on Leads and Deals require manual discovery via screen-share because no API schema documentation exists. We schedule a guided session where the customer walks us through creating a new Lead and Deal record, showing all visible fields and field settings. We then configure equivalent custom fields in Nutshell Settings (People, Company, or Lead tabs depending on object) using Nutshell's supported field types: text (225 char max), long text, currency, and date. Value transformations are applied where data types differ between the two platforms.