Migrate from Sugar Sell to Nutshell

Sugar Accounts map directly to Nutshell Accounts. The Account Name, website, phone, industry, and address fields transfer 1:1. Nutshell uses a single address block per Account; Sugar address fields (billing_street, billing_city, etc.) are concatenated into the Nutshell mailing_address string during transform. Account is the first object imported because Contacts, Opportunities, and Activities reference it as a parent.

Sugar Contacts map to Nutshell Person records in the Contacts section. We resolve the Contact-to-Account relationship via the account_id foreign key and attach the Person to the migrated Account. Sugar contact roles on Account-Contact relationships (e.g., 'Decision Maker', 'Technical Buyer') transfer as custom text fields on the Person record. Title, email, phone, and address fields migrate directly.

Sugar Leads map to Nutshell Person records in the Leads section. We preserve the full Lead status lifecycle (New, Assigned, In Progress, Converted, Dead) in a custom field sugar_lead_status__c on the Nutshell Person. Any Sugar Predict AI lead scoring values transfer to a custom numeric field lead_score__c for post-migration prioritization.

Sugar Opportunities map to Nutshell Opportunities with amount, name, date_closed, and sales_stage preserved. Sugar stage values (Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost) remap to Nutshell stage values during the transform. The probability field transfers to a custom field probability__c on Nutshell Opportunity because Nutshell does not expose probability as a standard field, but the stage order implicitly drives win likelihood.

Sugar's separate Calls, Meetings, and Tasks modules each map to Nutshell Activity records with a type flag (call, meeting, or task). We resolve the parent record reference using the foreign key fields (contact_id, lead_id, opportunity_id) and attach the Activity to the migrated Nutshell Person or Opportunity. ActivityDate and duration fields preserve the original timestamp and length. Calls migrated as Activity with type=call; meetings as type=meeting; standalone tasks as type=task.

Sugar Quotes with line items migrate to Nutshell Quotes. Sugar's quoted_line_items (product name, quantity, unit_price, discount) transfer directly to Nutshell Quote Line Items. Tax and discount fields from Sugar carry over. PDF attachments on Sugar Quotes migrate as file attachments on the Nutshell Quote via Nutshell's file upload API.

Sugar Product Catalog entries map to Nutshell Products with name, description, price, and product_code preserved. Sugar Manufacturers and Product Types map to Nutshell custom fields on Product (manufacturer__c, product_type__c). The Nutshell Products feed into the Nutshell Quotes tool for pricing quotes.

Sugar Cases migrate to Nutshell Cases with subject, description, priority, status, and resolution fields preserved. The Account and Contact linked to the Case resolve via the Account and Person lookup. Bug Tracker-specific fields (severity, version, resolution type) from Sugar Advanced and Premier migrate as custom fields on Nutshell Case.

Sugar Users map to Nutshell Users by email address match. Any Sugar User without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Team membership from Sugar (which determines record-level access) transfers to Nutshell Teams via the API. Role and status fields from Sugar carry over as custom fields on the Nutshell User record.

Sugar Notes (text and file attachments) migrate to Nutshell Notes linked to the parent record via the relationship field (account_id, contact_id, opportunity_id). Text notes transfer as Note body. File attachments are extracted from the Sugar file system or API response, re-uploaded to Nutshell via the file attachment API, and linked to the same parent record.

Sugar Tags stored as string values on records extract and deduplicate into a Nutshell Tags collection. We recreate each unique tag in Nutshell and relink the tag associations to the migrated Account, Person, or Opportunity records. Tags used for lead segmentation transfer as Nutshell List memberships in addition to tag labels.

Sugar Studio custom fields require vardef file extraction before migration. We read the custom field name, type, module assignment, and default value from the vardef, then pre-create matching custom fields in Nutshell via the customFields API on the corresponding object (Lead, Account, Contact). Vardef-enforced required fields map to required: true in Nutshell. Dropdown or multi-select types in Sugar map to Nutshell custom field picklist options. This step must complete before any data import because custom field values cannot insert into a field that does not yet exist.