Migrate from SendCloud to Microsoft Dynamics 365 Sales

SendCloud Shipment and Parcel records carry structured ship-to address data (recipient name, company, street, city, postal code, country). We map unique recipient addresses to Dynamics 365 Accounts (using company name or recipient name as the Account Name) and individual recipients to Contacts linked to that Account. Address validation rules differ between platforms; we flag mismatches where SendCloud freeform address fields exceed Dynamics 365 field length limits and apply truncations with a validation log.

SendCloud Parcel records contain tracking number, weight, dimensions, status, carrier, and timestamps. We map active or recently closed Parcels to Dynamics 365 Task records attached to the relevant Account or Contact, with the tracking number stored in the Task Subject or a custom field, carrier name in a custom Carrier__c field, and parcel status as Task Status. Historical parcels from completed shipments migrate as read-only Note records so the Account timeline reflects full fulfillment history without cluttering open activity views.

SendCloud Return records track inbound parcel flows including RMA status, return reason codes, and carrier. We map Returns to Dynamics 365 Cases when Service Cloud is included in the destination license, using Case Subject to carry the return tracking number, Case Reason for the return reason code, and Case Origin for the carrier. If Service Cloud is not included, Returns migrate as Task records with a Return__c custom field flag. Return label templates and portal settings do not export from SendCloud; we inventory these in the delivery documentation for manual reconfiguration.

SendCloud Shipments group one or more Parcels sent to the same recipient and carry the shipping method, service level, and estimated delivery date. We map each Shipment to a Dynamics 365 Task attached to the parent Account, with the Task Subject carrying the shipment reference, and linked Parcels surfacing as sub-Tasks or related Note records. This preserves the shipment grouping hierarchy in the destination CRM timeline.

SendCloud user accounts include name, email, and shipping operation role assignments. We extract the full user list and match by email against the destination Microsoft Dynamics 365 Sales org's User table. SendCloud role assignments do not map to Dynamics 365 security roles directly; we deliver a written role matrix showing the source role and a recommended Dynamics 365 security role equivalent for the customer's admin to assign post-migration.

SendCloud carrier routing rules define which carrier services apply per shipment corridor. We map carrier names and service levels to custom text fields (Carrier__c, ServiceLevel__c) on the Activity or Case records where shipment data lands. Carrier-specific negotiated rates stored within SendCloud are not accessible for export; we flag this explicitly in the scope document and note that rate re-negotiation with carriers is required at the destination.

SendCloud supports custom fields on Parcel and Return objects at Growth tier and above. We inventory all custom field schemas during scoping, map each to an equivalent Dynamics 365 custom field (Custom__c naming convention), and deploy the destination schema into a Sandbox before production migration. Custom field data types are matched to Salesforce field types (text, number, date, picklist) with a validation log for any unsupported format conversions.

SendCloud webhooks notify external systems of Parcel status changes, shipment events, and return updates. These webhook subscriptions are account-bound credentials tied to SendCloud's endpoint registration system and do not export as transferable configuration. We inventory all active webhook endpoints, payloads, and retry settings and deliver them as a documented list so the customer can re-register equivalent Power Automate flows, Azure Functions, or third-party webhook receivers in Dynamics 365 or the connected ERP.

SendCloud's native integrations with Shopify, WooCommerce, Magento, and other shop platforms connect order data to label creation. These integrations are SendCloud-specific OAuth credentials and do not transfer to Dynamics 365. We inventory active integrations and flag which require new API credentials. The customer configures Dynamics 365 integrations with their shop platforms as a post-migration step, or retains SendCloud as a fulfillment layer with Dynamics 365 handling customer and sales management.