Migrate from Maple CRM to Nutshell

Maple CRM Leads with source, status, assigned executive, follow-up dates, and custom intake data map directly to Nutshell Leads. Jurisdiction-specific intake fields (IRCC stream, visa type, country of origin) migrate to custom fields on the Nutshell Lead record. We preserve the Maple Lead status as a custom field hs_original_status__c for reconciliation. The migration creates Leads before People to support the Nutshell import ordering convention.

Maple CRM Client records hold contact details, address, nationality, passport data, and links to multiple open Cases. Client maps to Nutshell Person, which stores contact information, company association, and custom fields. We migrate Clients before Cases to satisfy foreign-key lookups in Nutshell's People-centric model. Passport expiry dates and nationality fields migrate to custom fields on the Person record since Nutshell does not have native passport tracking.

Maple CRM Cases link to a Client and track process stages (Application, Review, Submission, Approval, Denial/Appeal). Nutshell has no native Case object, so we map each Case to a Nutshell Deal with custom fields preserving the original case context: case_id__c, visa_type__c, jurisdiction__c, application_stage__c, and ircc_reference__c. For Clients with multiple active Cases, we create one Deal per Case to preserve the per-application record. The original Maple case stage becomes a custom picklist field rather than a Nutshell pipeline stage, since Nutshell's pipeline stages are sales-oriented.

Documents attach to Cases or Clients and include intake forms, passports, proof of funds, and visa applications. File attachments migrate as binary blobs linked to the parent Deal (from Case) or Person (from Client). Document type metadata (passport, application form, proof of funds) migrates to a custom field doc_type__c on the attachment record. We preserve upload date and the related record reference. Large document repositories may extend timeline depending on total blob size.

Maple CRM Quotation Builder creates PDF quotations linked to Deals or Orders. We migrate quotation line items, pricing, and status as custom fields on the Nutshell Deal: quotation_amount__c, quotation_status__c, and quotation_date__c. The PDF itself does not migrate; only the underlying data record transfers. If the customer requires PDF preservation, we attach the rendered PDF as a file on the Deal after migration.

Maple CRM Invoice Builder tracks invoice generation, payment status, and instalment schedules. Invoice records map to custom fields on the related Nutshell Deal: invoice_number__c, invoice_amount__c, payment_status__c, instalment_schedule__c, and outstanding_balance__c. Historical paid invoices preserve their status for financial audit. Nutshell does not have a native accounting module, so billing data lives in custom fields on the Deal record.

Contracts and Annual Maintenance Contracts link to Clients and track service terms, renewal dates, and pricing. These map to custom fields on the Nutshell Deal derived from the original Client or Case: contract_type__c, contract_start_date__c, contract_end_date__c, renewal_date__c, and contract_value__c. Renewal scheduling is preserved as a date field; Nutshell does not have native contract renewal automation.

Support Request records from Maple CRM's separate module migrate to Nutshell Tasks. We transfer status, priority, assignee (mapped via email to Nutshell User), and timestamps (created, modified). SLA and TAT escalation rules do not migrate; these are platform-specific configurations documented for rebuild in Nutshell's Task automation features post-migration. Support Request queue assignments map to Nutshell User ownership of the Task record.