Migrate from SendCloud to Pipedrive

SendCloud stores ship-from and ship-to addresses linked to Shipments. Ship-to addresses map to Pipedrive Person records (address fields in the Person object). Ship-from addresses (merchant warehouse or fulfillment locations) map to Pipedrive Organization records representing the business entity. We preserve original address formatting, validate against Pipedrive field length limits, and flag addresses with incomplete data (missing postal code, country) for pre-migration cleanup.

SendCloud Parcel records with a linked customer email or reference number map to Pipedrive Note records attached to the corresponding Person. The Note body carries parcel reference, carrier, tracking number, weight, dimensions, and status. This preserves shipment context against the customer record rather than creating a standalone shipping object that Pipedrive does not support. We flag that tracking status updates and live tracking URLs are not migrated as active webhooks; these require reconfiguration at the destination or with the new carrier integration.

SendCloud Shipment records map to Pipedrive Task records representing shipping events linked to the Person. The Task subject carries shipment reference, carrier, and estimated delivery date. Shipment status changes (dispatched, in transit, delivered) migrate as historical Task completion records with timestamps preserved. Active in-transit shipments at migration time are flagged for manual status update post-migration.

SendCloud Return records map to Pipedrive Note records on the Person (carrying return reason, RMA number, return label status) plus a Task record for the return processing activity. Return portal status (pending, received, refunded) migrates as a custom field choice on the Note. Return workflow configurations (reason codes, label templates, return-to-address) are inventoried but not migrated; these require manual reconfiguration at the destination platform or a dedicated returns management tool.

SendCloud custom fields added to Parcels and Returns on applicable plans map to Pipedrive custom fields on Person and Organization. We inventory the custom field schema during scoping, match field types (text, number, date, picklist) to Pipedrive equivalents, and pre-create fields in Pipedrive before migration. Custom fields with no equivalent Pipedrive type are flagged for customer review during scoping.

SendCloud user accounts (with role assignments tied to shipping operations) map to Pipedrive User records for team ownership mapping. We extract the user list by email, map to existing or provision new Pipedrive users, and use the User mapping to set OwnerId on migrated Person and Organization records. Permission structures are platform-specific and require manual review post-migration.

SendCloud carrier integrations (DHL, UPS, FedEx, regional carriers) do not have a Pipedrive equivalent object. We map carrier names to a Pipedrive custom picklist field on the Person or Note record so that shipment history retains carrier attribution. Carrier-specific rate negotiated rates are not migrated (stored in SendCloud's internal rate tables); this is flagged during scoping as requiring direct carrier re-negotiation or rate-porting.

SendCloud webhook endpoint configurations (Parcel status change, shipment event, return update) are exported as a written inventory document listing endpoint URLs, event types, and payload schemas. We do not recreate webhooks in Pipedrive because Pipedrive does not have an equivalent webhook-driven shipping notification system. The inventory is handed off for the customer's developer to integrate with their new shipping platform post-migration.

SendCloud native integrations with Shopify, WooCommerce, Magento, PrestaShop, and other shop platforms are inventoried with active API credential references. We document which integrations require new credential rotation and new webhook endpoint updates post-migration. Pipedrive's native Shopify and WooCommerce integrations handle CRM-side sync; the shop platform must be reconnected to Pipedrive with updated credentials.

SendCloud label format preferences (branding, label size, carrier-specific formatting) are documented as a configuration inventory rather than migrated data. Pipedrive does not generate shipping labels. The inventory is handed off for the customer to configure in their new shipping platform or carrier dashboard.