Migrate from SellingLane CRM to Nutshell

Discovery and field audit

We audit SellingLane CRM across Buyer records, Lot catalogs, bid histories, registration records, auction event groupings, and all custom field definitions. Because SellingLane's custom field schema is not publicly documented, we query the platform's field configuration endpoint to generate a complete field manifest before mapping. We pair this with a Nutshell plan review (Foundation through Enterprise) to confirm custom field limits and plan allocation. The discovery output is a written migration scope with record counts, custom field inventory, and a dependency graph showing which objects must load before others.

Staging and relational resolution

We extract bid records and registration records into our staging database and resolve the Buyer-to-Lot relational links before any import begins. For each bid, we match the buyer_id to a Nutshell Person record and the lot_id to a Nutshell Product record, storing both resolved references as foreign keys in our staging schema. This step is required because Nutshell does not support the same Buyer-Lot join table model natively; we reconstruct the relationship using custom fields and activity linking rather than a native relational object.

Custom field creation in Nutshell

We create all required custom fields in Nutshell before data import begins. This includes custom fields on People for bidder ID, verification status, and buyer tier; custom fields on Products for lot number, reserve price, starting bid, lot status, auction event name, auction event date, and auction event location; and custom fields on Activities for bid amount, bid type, bid timestamp, and payment method. Field types are matched to Nutshell's supported types (text, number, date, picklist) during the field-mapping phase.

Test migration to Nutshell sandbox

We run a full migration into a Nutshell sandbox using production-like data volume. The customer reconciles record counts (Buyers in, Lots in, Activities in), spot-checks 20-30 random records against the SellingLane source, and validates that bid relational links, verification status values, and auction event groupings transferred correctly. Any mapping corrections happen in the sandbox before production migration begins.

Production migration in dependency order

We run production migration in record-dependency order: Nutshell Users (validated against SellingLane staff), People (from Buyers), Products (from Lots), Activities (bids and registrations with resolved Person and Product references), and Deals (for won lots if the customer chooses to represent payments as deals). Attachments load last after record IDs are confirmed. Each phase emits a row-count reconciliation report before the next phase begins.

Cutover, validation, and automation rebuild handoff

We freeze SellingLane writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver a written inventory of any SellingLane workflows, automations, or trust-account logic that could not migrate, with a rebuild recommendation for the customer's admin. We do not rebuild SellingLane automations as Nutshell automations inside the migration scope; that is a separate engagement or an internal admin task.