Migrate from SendCloud to monday CRM

SendCloud stores ship-to addresses as structured objects linked to Parcels and Shipments. We extract address records keyed by recipient email and name, creating one Contact per unique recipient. The Contact's email, phone, and name fields are populated from the SendCloud address; any additional address fields map to the Contact's mailing address columns. When a single email appears across multiple Parcels (repeat customers), we deduplicate to one Contact with the most recent address preserved.

SendCloud ship-from addresses associated with merchant fulfillment locations map to Monday.com Companies representing the business's own locations or warehouse entries. For merchants who track supplier ship-from addresses, these become supplier-related Companies. Company name is derived from the address label or carrier origin reference when available.

Each SendCloud Parcel becomes a Monday.com Item on a dedicated Shipments board. Parcel reference number maps to Item name. Weight, dimensions, and carrier service level map to number and text columns. Parcel status (pending, label_created, shipped, in_transit, delivered, returned) maps to a Status column with values matching the SendCloud lifecycle. The Item is linked to the Contact record via a Lookup column pointing to the Contact derived from the ship-to address.

SendCloud Shipments group one or more Parcels under a single carrier dispatch event. We model Shipments as Groups within the Monday.com Shipments board, with each Group named by carrier and dispatch date. Parcels within a Shipment become Items within that Group, preserving the SendCloud one-to-many relationship.

SendCloud Return records become Items on a Returns board linked to the original Shipment Item via a Lookup column. Return status (requested, approved, label_sent, received, refunded) maps to a Status column. Return reason codes migrate as a Labels column or text field. The Item links back to the originating Contact via a Lookup relationship so the return history is visible in context of the customer record.

SendCloud carrier routing rules and carrier integrations do not have a direct Monday.com equivalent. We inventory active carrier connections during scoping and provide a written map of which carriers are active, their routing priority, and the carrier API credential status. The customer recreates carrier routing logic inside Monday.com automations or documents it as part of their operations playbook. Carrier names migrate as a text column on the Shipments board for reference.

SendCloud custom fields on Parcels (available on Growth and above plans) map to custom columns on the Monday.com Shipments board. We inventory the full custom field schema during scoping, map each to the closest Monday.com column type (text, number, date, checkbox, dropdown), and pre-configure the columns before import so that custom data populates on first load.

SendCloud webhook endpoints for tracking notifications and shipment events are exported as a written inventory document listing each endpoint URL, event type, and active/inactive status. Monday.com does not have an inbound webhook receiver for shipping events, so these integrations require rebuild using Monday.com's outbound integration options (Zapier, native integrations) or direct API connections from the shop platform. We do not migrate webhooks as live connections.