Migrate from SendCloud to Nutshell

Scoping and plan audit

We audit the SendCloud account for current plan tier, parcel and return volume, active custom fields on Parcels, configured carrier routing rules, active webhook subscriptions, and connected shop platform integrations. We pair this with a Nutshell plan review to confirm custom object availability (available from all Nutshell paid plans) and identify any custom field type constraints. The scoping output is a written migration scope document with a record-count estimate and a list of every integration requiring reconfiguration after cutover.

Address extraction and deduplication design

We extract all ship-to addresses from SendCloud Shipment and Return records using the SendCloud API (parcels endpoint with shipment data). We design a deduplication strategy using postal code, recipient company name, and recipient name as the primary match keys because shipping address data frequently has formatting inconsistencies. We run a deduplication pass before any Nutshell import to prevent duplicate Company and Person records from forming during migration.

Custom object schema creation in Nutshell

We create the Shipment_History__c and Return_History__c custom objects in Nutshell before any data import, including all custom fields (carrier, service level, tracking number, status, timestamps, return reason code, RMA number). We also create any custom fields on Company or Person to carry carrier routing preferences or shipping pattern data extracted from SendCloud. Schema is created in the customer's Nutshell environment before record import begins.

Company and Person migration

We run the address extraction output through the deduplication pass, then import deduplicated Company records into Nutshell first. Person records are imported second, linked to the parent Company via the AccountId lookup. Each Person record carries the original SendCloud shipment reference as a custom field for traceability back to the source system.

Shipment and Return history migration

We migrate Parcel and Return records as custom Shipment_History__c and Return_History__c records linked to the parent Person or Company. Tracking URLs are stored as URL fields on the custom object so users can click through to the carrier tracking page directly from Nutshell. Return reason codes are mapped to the picklist values configured in the custom schema during step 3.

Webhook and integration inventory delivery

We deliver a written inventory document listing every active SendCloud webhook endpoint, the event type, the current target URL, and the recommended replacement setup in the customer's post-migration shipping platform. We also list every active shop platform integration (Shopify, WooCommerce, Magento, etc.) with the current API credential scope and a reconnection checklist. The customer's developer or shipping administrator completes reconnection post-migration. We do not perform the reconnection work inside the migration scope.

Cutover and reconciliation

We freeze SendCloud write access during the final cutover window, run a delta extraction for any records modified since the initial export, import the delta into Nutshell, and run a final row-count reconciliation against the extraction totals. We deliver the reconciliation report to the customer's admin. Any duplicate records created by the Nutshell import-only limitation are flagged for manual merge. We do not provide post-migration admin support or training as standard scope; these are separate engagements.