Migrate from Lemon Tech to Nutshell

Discovery and export capability assessment

We audit the Lemon Tech environment across all active entity types (standard and custom), Matter records, SQL Wrapper definitions, and user accounts. We identify any export capability limitations tied to the customer's pricing tier and map the export function's output format for each entity type. We pair this with a Nutshell API review to confirm field type availability for each source field. The discovery output is a written migration scope with an entity-to-Nutshell-object mapping table, a SQL Wrapper complexity classification, and a custom entity disposition plan for each custom entity type.

Chunked export sequencing from Lemon Tech

We run Entity exports in dependency order: Contacts first (to populate People in Nutshell), then standard Entities (to populate Accounts), then Matters (to populate Opportunities with resolved Person and Account IDs), then custom entities (to populate custom fields or document standalone types), and finally SQL Wrapper data and attachments. Each export is chunked by entity type, with large datasets split into batches of 1,000-5,000 records to avoid server task timeouts. We validate row counts against the Lemon Tech admin's expected record counts before proceeding to import.

Nutshell schema pre-configuration

We pre-create any required Nutshell custom fields on Person, Account, and Lead before record import begins. This includes creating text, long text, currency, date, and dropdown custom fields matching the Lemon Tech source field types. We do not create custom objects in Nutshell because Nutshell does not support them; standalone custom entity types are documented with their recommended disposition (consolidate into a standard object, handle via external tool, or table as a Note type) for the customer to address post-migration.

Sandbox migration and reconciliation

We run a full migration into a Nutshell sandbox environment (or a staging account if sandbox is not available on the customer's tier) using production-like data volume. The customer's team reconciles record counts, spot-checks 20-30 records against the Lemon Tech source for accuracy, and validates that custom field values populated correctly. Any mapping corrections and custom field additions happen in this phase. We do not proceed to production until the customer signs off on the sandbox reconciliation.

Production migration in dependency order

We run production migration in record-dependency order: Users (validated), People (from Contacts), Accounts (from standard Entities), Leads (if any source records map to Lead), Opportunities (from Matters with resolved PersonId and AccountId), custom field data (appended to the relevant standard object), SQL Wrapper data (as Notes linked to parent records), and attachments (as Notes with original filename metadata). Each phase emits a row-count reconciliation report before the next phase begins. We freeze Lemon Tech write access during the final migration window to prevent delta records from accumulating.

Cutover, validation, and automation handoff

We run a final delta migration of any records created or modified during the cutover window, then enable Nutshell as the system of record. We deliver a written inventory of all migrated objects, record counts, and any Lemon Tech entity types that were classified as standalone and require manual post-migration configuration. We do not rebuild Lemon Tech workflows or automations; Nutshell's automation model (Tasks, Reminders, and external integrations) differs enough that we document the equivalent approach rather than attempt automated translation. We support a three-day hypercare window for reconciliation issues raised by the customer's team.