Migrate from Leadtrekker Lead Management to Nutshell

Discovery and API probe

We audit the Leadtrekker account to extract the full record inventory: lead count, activity count (notes, calls, emails), user roster, user group membership, custom field inventory (extracted via API), and any visible assignment rules or autoresponders. We run an API discovery probe to determine available endpoints, authentication method, and safe request pacing. We cross-reference this with a review of the Nutshell API documentation to confirm available import endpoints for People, Companies, Leads, and Activities. The discovery output is a written migration scope with record counts, field mapping draft, and a list of any Leadtrekker configuration items (notifications, assignment rules, autoresponders) requiring manual handoff.

Schema design and Company extraction

We design the Nutshell custom field schema to accommodate any Leadtrekker custom fields not covered by Nutshell's native Person fields. We then run the first-pass data extraction: deduplicating all company names from the Lead records and creating Nutshell Company records. This pass produces a company_id mapping that is used in the second-pass Person import. Any ambiguous or missing company names are flagged in a data-quality report for the customer to resolve before the Person import.

User and team provisioning

We extract the Leadtrekker user roster and match each user by email against the Nutshell destination account. We create a mapping table and flag any Leadtrekker users not yet present in Nutshell. The customer's admin provisions missing users and sets up Nutshell Teams based on the user-group-to-team mapping we deliver. Nutshell sends invitation emails to each provisioned user for account activation. Migration cannot proceed past this step because OwnerId references on Person records require a valid Nutshell User.

Person and Lead import

We import Leadtrekker Leads into Nutshell as Person records, resolving the company_id from the Company extraction pass. Email serves as the dedupe key. We import all native fields (name, email, phone, address, source, status, owner) and map custom fields to the Nutshell custom field schema. For leads that the customer designates as unqualified prospects, we import as Nutshell Lead records rather than People. Each phase emits a row-count reconciliation report.

Activity timeline migration

We migrate Leadtrekker activities (notes, calls, emails) against the correct Nutshell Person by resolving the Lead email to the imported Person record. Activities that reference a Lead whose email did not match a Person (for example, an activity on a Lead that was discarded during deduplication) are flagged in a separate reconciliation queue. Activity timestamps preserve for timeline ordering. Call duration and disposition map to custom fields on the Nutshell Activity record.

Cutover, validation, and handoff

We freeze Leadtrekker writes during cutover, run a final delta migration of any records modified during the migration window, then mark Nutshell as the system of record. We validate record counts across all objects and spot-check a sample of Person records against the Leadtrekker source. We deliver the notification settings reference checklist, the automation inventory document, and the user-group-to-team mapping table. We support a three-day post-cutover window to resolve reconciliation issues. We do not rebuild Leadtrekker assignment rules or autoresponders in Nutshell; that work is documented for the customer's admin.