Migrate from Customer Database App to Nutshell

Customer Database App Contact records with a company name or domain field map to both a Nutshell Company and a Person record linked to that Company. Contacts with no company affiliation map to a standalone Person. We infer the company-association logic from the exported column headers during discovery. The email address, phone, and address fields map directly to Nutshell's standard Person fields; all remaining custom fields map to Nutshell custom fields scoped to the Person object.

Every Customer Database App contact supports unlimited user-defined fields with no enforced schema. We infer the active field list from the exported CSV column headers at discovery, map each to a typed Nutshell custom field (Text, Long Text, Currency, Date, Checkbox, or Dropdown depending on inferred value format), and create the fields in Nutshell before import. Free-text fields containing commas are sanitized during transform to prevent CSV parsing issues. Fields added or renamed after the last export are flagged for customer confirmation before loading.

Customer Database App's Kanban-style pipeline with user-defined stage labels maps to Nutshell's pipeline stage configuration. Stage names and ordering migrate directly. We create Nutshell pipeline stages in advance using the names and sequence from the source export. If Customer Database App has deal value or close date fields, we map those to Nutshell's deal amount and expected close date on the associated Person or Company record.

Customer Database App stores customer groups and tags as comma-separated label strings on each contact record. We split these into individual Nutshell Tag records during transformation, creating the tag in Nutshell if it does not already exist and associating it with the target Person or Company record via Nutshell's tag linking mechanism.

Birthday is stored as a date field on the Customer Database App contact record. We map it to a Nutshell custom date field (e.g., birthday_date__c) on the Person object. Nutshell does not have a native birthday-specific field, so we use a labeled custom date field and document the field name for the customer's admin to optionally rename or add a birthday-specific label.

Customer Database App contact images and PDF exports of individual records can be bundled into a ZIP archive alongside the CSV. We attach each contact's image or PDF to the corresponding Person record in Nutshell using Nutshell's attachment mechanism. This requires the customer to generate the PDF export from Customer Database App before providing the file archive.

Vouchers are a standalone object in Customer Database App with no direct equivalent in Nutshell. Voucher balances are not exported via CSV. We do not migrate voucher data. We recommend exporting vouchers as a separate supplemental CSV for manual re-entry in the destination system or a dedicated voucher management tool.

Caller-ID logs and call history in Customer Database App are transient device-level records that are not exported via CSV or VCF. These do not migrate. We recommend documenting call-handling procedures separately and using Nutshell's built-in call logging (available on all tiers) to start fresh call records post-migration.