Migrate from Kordeva to Nutshell

Kordeva Contact records map to Nutshell Person (the standard CRM contact object). Standard fields (name, email, phone, address) transfer directly. Any custom contact-level attributes from Kordeva's Custom Fields API migrate as Nutshell custom fields on Person, which Nutshell supports for People, Companies, and Leads. We enumerate every distinct custom field definition during discovery and create matching Nutshell custom fields before the Person import batch begins.

Kordeva Company records map to Nutshell Company without renaming. The company-contact association is preserved by resolving the Kordeva contact-company link and setting the Nutshell Person's Company field on insert. Custom company-level attributes from the Custom Fields API migrate as Nutshell custom fields on Company. If Kordeva stores multiple contacts per company, all linked Person records reference the same Nutshell Company record on migration.

Kordeva Deal records map to Nutshell Deal with deal amount, close date, owner, and associated contact/company lookups preserved. Pipeline stage names migrate as text values in Nutshell's stage field. Pipeline layout and stage-to-stage configuration in Nutshell is a separate UI step that the customer's admin configures before migration or during the sandbox validation pass.

Kordeva pipeline stage names become Nutshell pipeline stage labels. We carry the original stage sequence and probability values from Kordeva as metadata and provide a written stage-mapping worksheet that the customer's admin uses to configure the Nutshell pipeline layout post-migration. Stage order and probability do not automatically transfer because Kordeva's stage model and Nutshell's pipeline configuration use different internal representations.

Kordeva activity records (call logs, email records, tasks, meeting records) attached to Contacts and Deals migrate to Nutshell Activities linked to the corresponding Person and Deal via Nutshell's activity associations. Activity timestamps preserve the original Kordeva created_at date for timeline integrity. Activity types map to Nutshell's activity type field (call, email, meeting, task). Note: Kordeva's UI export may not capture full activity history; we test export completeness during discovery and flag any gaps before migration begins.

Kordeva Custom Fields API extended attributes on Contacts, Companies, and Deals migrate as Nutshell custom fields. Field types (text, number, date, checkbox, dropdown) are mapped to equivalent Nutshell field types during schema design. We enumerate the full custom field schema during discovery, create the destination fields in Nutshell, and validate type compatibility before the Person, Company, and Deal import batches run.

Kordeva includes accounts and invoicing in the Regular tier. Invoice records, line items, and payment status are migratable as structured records but require field-level mapping because invoicing schemas vary significantly between platforms. We map invoice header fields to Nutshell Company custom fields and invoice line items to a structured format the customer's accounting team documents post-migration. Full accounting record migration requires a separate scope if invoice PDFs or line-item detail are required in the destination.

Kordeva Owners referenced on Contact, Company, and Deal records are resolved by email match against Nutshell User accounts. Any Kordeva Owner without a matching Nutshell User is placed in a reconciliation queue for the customer's admin to provision before the Person import batch runs. Owner assignments on Deals and Activities resolve after User provisioning is complete.