Migrate your SendCloud data

Parcels are the core transactional unit in SendCloud. Each Parcel carries weight, dimensions, a reference number, status, and links to a Shipment and carrier. We export Parcel records via CSV or API and map them to equivalent objects at the destination. Tracking history is preserved as a Parcel property.

Shipments represent the logical grouping of one or more Parcels sent to the same recipient address. Shipment records include the destination Address, shipping method, service level, and estimated delivery. We migrate Shipment-to-Parcel relationships intact so multi-parcel orders remain grouped at the destination.

Return requests track the inbound flow of parcels back to the merchant. SendCloud's return portal generates return labels and tracks RMA status. We export return data including return reason codes, carrier used, and resolution status. Return workflows at the destination require reconfiguration of return label templates.

Labels are generated per Parcel via carrier API calls and include barcode data, carrier-specific formatting, and optional branded elements. We do not migrate label binary files directly; instead we preserve label format settings and re-generate labels at the destination using the new carrier credentials.

Ship-from and ship-to addresses are stored as structured objects linked to Shipments and Returns. We preserve address records to pre-populate destination address books, noting that validation rules differ by carrier and destination platform.

Carriers are defined within SendCloud's routing rules and integration connections. We map carrier-to-carrier between platforms, but merchant-specific negotiated carrier rates are SendCloud-stored values and do not automatically transfer as the merchant's new contracted rates.

Custom fields can be added to Parcels and Returns on certain plans. The custom field schema is account-specific. We inventory all custom fields during scoping, map them to equivalent custom properties at the destination, and flag any field types that are not supported by the target platform.

SendCloud's webhooks notify external systems of Parcel status changes, shipment events, and return updates. We export webhook endpoint configurations so they can be recreated at the destination, though the destination platform's webhook delivery mechanism may differ.

User accounts in SendCloud include role assignments tied to shipping operations. We migrate user lists to map team ownership at the destination, but permission structures are platform-specific and require manual reconfiguration.

Native integrations with Shopify, WooCommerce, Magento, PrestaShop, and other shop platforms connect order data to SendCloud. We inventory active integrations and flag which require new API credentials at the destination. E-commerce platform webhook connections also need updating post-migration.