Migrate from Sage CRM to Nutshell

Sage CRM Company records map directly to Nutshell Organization. The company_name, address fields, phone, website, and industry classification migrate as typed fields. We use company_name as the dedupe key during import. Organization must be imported before People because Nutshell's People records link to Organization via a required reference field. Custom Company fields map to Nutshell Organization custom fields, subject to the plan's custom field limits (Starter: limited, Pro and above: more fields).

Sage CRM Contact records map to Nutshell People with the PrimaryCompanyLink foreign key resolved to the target Nutshell Organization ID. Standard fields (name, email, phone, title, address) migrate directly. Custom Contact fields map to Nutshell People custom fields. We apply Sage CRM's match-rule configuration during scoping to identify duplicate contacts and either merge or flag for customer review before import.

Sage CRM's separate Lead entity has its own lifecycle stages, qualification fields, and source tracking that do not map 1:1 to any Nutshell object because Nutshell uses a unified People record with a status field. We map Sage CRM Lead records to Nutshell People with a lead status value set from the Sage CRM lead status or a custom lead stage field. The customer chooses the target status value during scoping. Source tracking data (lead source, campaign reference) migrates to Nutshell People custom fields if available on the plan tier.

Sage CRM Opportunities map to Nutshell Deals. The pipeline stage name maps to Nutshell's pipeline stage values. Amount, expected close date, owner assignment, and custom opportunity fields migrate directly. Sage CRM's multi-currency amounts are stored as decimal values and migrate as-is; currency assignment is set at the Nutshell account level. Closed-won and closed-lost reasons map to Nutshell Deal notes or custom fields since Nutshell does not have a native Loss Reason field.

Sage CRM Cases map to Nutshell Cases. Case severity, status, assignment, and description fields migrate directly. Threaded communications linked to cases in Sage CRM (stored in the Communication table with entity_type=Case) migrate as Nutshell Activity records attached to the corresponding Case. Custom Case fields map to Nutshell Case custom fields. Nutshell Cases is available on Pro and above plans; Starter plan customers map Cases to People notes or a dedicated Deal tag for customer service tracking.

Sage CRM Communication records (emails, calls, meetings, notes) are entity-type agnostic and link to Company, Contact, Lead, Opportunity, or Case. We export Communications by entity type, resolve the parent record's Nutshell ID at migration time, and create Nutshell Activity records (type: email, call, meeting, note) linked to the target Nutshell record. Timestamps and activity direction (inbound/outbound) preserve from the source. Large communication histories (over 200,000 records) require chunked API writes with rate-limit handling.

Sage CRM Custom Entities have their own fields and relationships and use internal table naming that differs from the UI display name. We inspect the entity schema via the Sage CRM API model service to build the field map. Nutshell does not support standalone custom objects, so Custom Entity data maps either to existing Nutshell objects via custom fields (if the plan allows sufficient fields) or to Notes attached to the related Company, Contact, or Deal record. The customer selects the strategy during scoping based on their custom entity complexity and Nutshell plan tier.

Sage CRM Users map to Nutshell Users by email match. We extract all active Sage CRM users referenced on records and match against Nutshell User emails. Sage CRM role-based security profiles (object and field access) have no direct Nutshell equivalent because Nutshell uses a simpler permission model with team-based access. We map Sage CRM user roles to Nutshell teams during scoping, and the customer's Nutshell admin assigns team membership post-migration. Inactive Sage CRM users who own records are migrated as inactive Nutshell users to preserve historical assignment.