Migrate from Civicrm to Nutshell

CiviCRM Individual subtype maps to Nutshell Person. We extract first_name, last_name, email (primary and secondary), phone (primary and secondary), address fields (street, city, state, postal_code, country), and the contact's preferred communication method. External identifier is preserved in a custom field for dedupe reference. Preferred language and prefix/suffix are not native Nutshell fields and migrate as custom Person fields.

CiviCRM Organization subtype maps to Nutshell Company. We extract organization_name, legal_name, email (primary), phone, address, and website. The CiviCRM display_name (often a shortened form of the legal name) maps to Company Name. Dedupe is performed on website domain match. SIC code and number of employees are not native Nutshell fields.

CiviCRM Household subtype has no Nutshell equivalent. Households in CiviCRM represent family units with a household name, household address, and member relationships. We split each Household into its constituent Person records, assigning the household address to each Person record. The CiviCRM household_name is preserved in a custom field for reference. The customer chooses during scoping whether to create one Person record per household or one per individual with the address merged.

CiviCRM Activity records (Email, Call, Meeting, Task subtypes) map to Nutshell's activity types. We extract activity_type_id, subject, details (body), activity_date_time, duration_hours/minutes, location, and assignee. Nutshell activity types are typed as Note, Call, Meeting, or Email. The CiviCRM activity_status maps to Nutshell's activity status (completed, scheduled, etc). Activities without a subject get a generated subject from the activity type and date.

CiviCRM single-record custom fields appear as fields on the parent entity via the API custom.* selector and map to Nutshell custom fields on the equivalent entity type. Nutshell supports Text (225 char max), Long Text, Currency, Date, Boolean, Number, and Single-Select for each entity type. Multi-record custom groups (prefixed Custom_) are loaded as separate row entries linked to the parent contact. We create Nutshell custom fields in the correct entity bucket (Lead, Person, Company) during pre-migration configuration. Supported field types are validated against Nutshell's field type list during mapping.

CiviCRM Groups map to Nutshell Lists (static segments). We extract group_name, group_type (mailing list, access control, smart group), and the GroupContact membership records. Smart (dynamic) groups cannot be fully reproduced without re-running the underlying query logic, so we document the smart group definition as a written specification for the customer to recreate as a Nutshell List filter. Regular Groups migrate as Nutshell Lists with direct contact membership.

CiviCRM Tags are flat labels that attach to any entity. We map the tag name and its entity_id link to Nutshell Tags. Multi-entity tagging requires separate association records per entity type. Tag naming conventions are preserved verbatim. Nutshell Tags are available on Person, Company, and Lead records.

CiviCRM Relationships (household member, employee-employer, spousal, etc.) connect two contacts bidirectionally. Nutshell has no native relationship object, so we evaluate the relationship type and map accordingly: employer-employee relationships may become a custom field on the Person record pointing to the Company; household member relationships are preserved in a custom field on Person. The relationship type label is preserved as a tag or custom field value. Bidirectional nature is lost (Nutshell does not auto-create the reverse link).

CiviCRM Contributions (donations, pledges, payments) have no Nutshell equivalent. Nutshell is not a fundraising or billing CRM. We export Contributions as a structured CSV archive containing contribution_id, contact_id, financial_type, total_amount, currency, receive_date, payment_instrument, check_number, card_type_id, and the contribution status. The archive is delivered to the customer for import into a dedicated fundraising tool (GiveWP, Donorbox, Salesforce Fundraising and Engagement, or similar). Contribution metadata is preserved but loses its real-time CRM context.

CiviCRM Membership records (type, status, start_date, end_date, source) can be migrated as a time-bounded custom record type. We map membership_type to a custom picklist on Person, membership_status to a custom status field, and start_date/end_date to date fields. Active membership status is preserved as a tag on the Person record. Recurring membership billing requires a separate payment tool since Nutshell does not handle recurring billing.