Migrate from Aurea CRM to Nutshell

Aurea CRM Contact records map directly to Nutshell Person. We use email address as the dedupe key. Standard contact fields (name, title, phone, address) map to their Nutshell Person equivalents. The Aurea contact record's parent Account lookup resolves to a Nutshell Organization that we create first so that the Person-Organization relationship is established at insert time.

Aurea CRM Account records map to Nutshell Organization. The organization name, website, industry, and address fields map 1:1. Aurea's parent-child account hierarchy is preserved as Nutshell Organization hierarchy via the Parent Organization lookup field where the destination plan supports it.

Aurea CRM Opportunity records map to Nutshell Deal. The deal name, value (amount), and close date transfer directly. Aurea's configurable pipeline stage labels require explicit mapping to Nutshell stage names; we confirm the stage mapping table during scoping and configure Nutshell stages before migration begins. Owner assignment migrates via email-to-User resolution.

Aurea CRM activity records (tasks, appointments, timeline entries) map to Nutshell Activity. Activity type from Aurea becomes the Activity type in Nutshell. The original timestamp is preserved on ActivityDate for timeline ordering. Call disposition and duration from Aurea phone-call activities migrate to Nutshell custom fields that we pre-create if those values are present in the source data.

Aurea CRM custom fields across all objects require field-level mapping to Nutshell custom fields, which must be pre-created in Nutshell before any data loads. Nutshell's custom field limits are plan-tier gated: Growth has fewer available custom fields than Pro or Sales Business. We audit the full custom field inventory during scoping, confirm the target plan tier, create the destination fields, and flag any fields that cannot be accommodated for manual handling or note consolidation.

Aurea CRM user and owner records map to Nutshell User accounts. We resolve owners by email match. Any Aurea owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Historical assignment ownership migrates as the Nutshell assigned_to field on Deals and Activities.

Aurea CRM Campaign records (including Aurea Campaign Manager data such as campaign type, status, and response metrics) have no direct Nutshell equivalent. We migrate campaign membership as structured data on the related Aurea Contact and Account records, stored as custom fields on Nutshell Person or Organization. Campaign-level metrics (impressions, responses) are stored as custom fields on the primary associated record or in a campaign reference document.

Aurea CRM partner relationship management records track channel partners with partner-specific quota and territory assignments. Nutshell has no native PRM object. We migrate partner data as Nutshell Person and Organization records with custom fields for partner tier, partner type, quota value, and territory name. The customer's admin defines these custom fields during scoping, and we map the Aurea partner-specific fields to the created destination fields.

Aurea CRM document management stores files linked to records. We extract attachment metadata (filename, linked record, file size, upload date) from Aurea's file store where accessible. File content migrates as attachment references if the destination Nutshell plan supports file storage. High-volume attachment migrations (over 1,000 files) are flagged during scoping because Nutshell's per-plan storage limits require advance planning.

Aurea CRM territory assignments and quota values are configurable per installation with no standard export format. We migrate these as custom fields on the relevant Nutshell User (for quota assignment) or Deal (for territory tracking) records. The specific field structure is confirmed during scoping based on what the Aurea administrator confirms as exportable.