Migrate from SuiteCRM to Nutshell

SuiteCRM Accounts map directly to Nutshell Companies. We extract name, industry, website, billing and shipping addresses, phone, and any custom fields created in SuiteCRM Studio. The account name becomes the Company name in Nutshell and is used as the dedupe key during import. Companies must be created before People imports so that the Company lookup relationship is satisfied at the moment of People insert.

SuiteCRM Contacts map to Nutshell People with the primary Account link resolved to a Company reference. We map first name, last name, email, phone, title, primary account link, and any Studio custom fields. Nutshell People stores both individual contact and lead data under one object with a status flag — we import Contact records with status set to customer or prospect depending on the source account relationship.

SuiteCRM Leads map to Nutshell People with status set to lead. We carry over lead status, lead source, and assignment fields. SuiteCRM's lead-to-contact conversion ratio is resolved by importing leads as People records with the lead flag set, preserving the full lead record history. If a lead has a prior activity history in SuiteCRM, we attach that as a note on the Nutshell People record since Nutshell's engagement model differs.

SuiteCRM Opportunities map to Nutshell Deals. The opportunity name, amount, close date, sales stage, probability, and parent Account link migrate to Nutshell Deal fields and pipeline stages. Stage values are mapped to Nutshell pipeline stages during import; SuiteCRM's probability field is preserved as a custom numeric field on the Deal since Nutshell's pipeline probability is configured per stage rather than per record.

SuiteCRM Products map to Nutshell Products if the destination Nutshell account uses Nutshell's built-in product catalogue. We extract product name, SKU (part number), cost, list price, and description. Products must be imported before any Quote line items that reference them so that the product reference is satisfied.

SuiteCRM Quotes have no direct Nutshell equivalent. Quote data — line items, pricing, terms — is exported as structured JSON and attached as a Note on the corresponding Nutshell Deal. The quote body is not imported as a live document; PDF generation is a post-migration step the customer's admin handles. We preserve the quote data structure for manual recreation.

SuiteCRM Invoice records (payment status tracking only, no accounting ledger) are exported as structured records and attached as Notes to the relevant Nutshell Company. The invoice amount, status, and date transfer. Full accounting data does not exist in SuiteCRM and must be sourced from the customer's accounting system post-migration. We flag this as a partial record and direct the customer to their finance system.

SuiteCRM Contracts with start/end dates and renewal status are mapped to Notes on the related Nutshell Company or Deal. The renewal date and contract terms are preserved as text within the note. If the customer uses SuiteCRM's contract tracking heavily, we recommend establishing a renewal date reminder in Nutshell manually post-migration.

SuiteCRM Cases (Bugs module) have no direct Nutshell equivalent. Case records are exported with status, priority, description, and resolution notes, then attached as Notes to the related Nutshell People or Company record. For teams using cases as a support tracker, we recommend a dedicated helpdesk tool post-migration; cases do not map cleanly to Nutshell's sales-centric model.

SuiteCRM Campaigns and their associated target lists do not have a Nutshell equivalent. Campaign metadata (name, type, status, start/end dates) is exported and attached as Notes to the related Company records. Email campaign response activity is extracted as activity logs and linked to the relevant Nutshell People records. Marketing automation rebuilt is out of scope.

SuiteCRM Studio custom fields are stored in extended database tables with the module name appended to the field name (e.g. account_type_c on Accounts). We scan the database for all custom field tables, extract their values, and map them to Nutshell custom fields on the corresponding object (Company, Person, Lead, or Deal). Field type mapping applies: text to Nutshell text, date to Nutshell date, picklist values to Nutshell picklist options.

SuiteCRM Documents store files on the server filesystem (typically /upload/) with database metadata. We extract the file blobs and their database metadata, then re-attach them to the corresponding Nutshell People, Company, or Deal record via the Nutshell API or Import2 attachment step. File permissions must be preserved during extraction; we validate checksums after extraction to confirm integrity. This step extends the migration timeline for file-heavy instances.