Migrate from SendCloud to Odoo CRM

SendCloud Parcel records map to Odoo Stock Picking records with move lines representing the shipped items. Each Parcel's weight, dimensions, reference number, status, and carrier information migrate as fields on the Stock Picking and stock.move records. Parcel status (shipped, in_transit, delivered, returned) maps to Odoo's picking state and move state fields. The SendCloud Parcel external_id is preserved as a custom field for reconciliation.

SendCloud Shipment records, which group one or more Parcels sent to the same recipient, map to Odoo Sale Orders. The recipient address from the Shipment becomes the Delivery Address on the Sale Order. If the customer does not already exist as an Odoo Contact, we create one from the shipment recipient data. Shipment carrier and service level map to Odoo's delivery method and shipping_cost fields on the Sale Order.

SendCloud Return records track the inbound flow of parcels back to the merchant. We map these to Odoo Stock Pickings of type 'return' linked to the original outbound Delivery Order. Return reason codes from SendCloud migrate to a custom picklist field on the return picking. Note that SendCloud return portal settings (reason code configuration, label templates) are not exposed via the API and require manual reconfiguration in Odoo after migration.

SendCloud stores ship-to addresses as structured objects on Shipments and Returns. Multiple shipments to the same address are consolidated into a single Odoo Contact record with the address set as the primary delivery address. Name, street, city, postal code, country, and phone migrate directly. Email addresses, if present on shipment recipient data, migrate as email fields on the Contact. We deduplicate by address hash to avoid creating duplicate Contact records for repeat customers.

SendCloud's sender address configuration, used as the ship-from origin on Parcels, maps to an Odoo Company record and a Warehouse record. The Warehouse address in Odoo must match the Address Name field in SendCloud exactly (case-sensitive) for return processing to work correctly. We flag this requirement during scoping and validate the name match before production migration begins.

SendCloud carrier routing rules and activated carrier integrations map to Odoo Delivery Carriers configured in Inventory > Configuration > Delivery Methods. We preserve the carrier-to-carrier mapping (which SendCloud carriers correspond to which Odoo delivery carrier integrations) in a written carrier routing table. Carrier-specific negotiated rates stored in SendCloud's internal tables do not transfer and are flagged as a high-severity gotcha for the customer to resolve directly with carriers post-migration.

SendCloud custom fields on Parcels (available on certain plan tiers) map to custom fields on the Odoo stock.picking model. We inventory all SendCloud custom field schemas during scoping, map them to Odoo custom fields with matching data types, and pre-create the destination schema before migration so that custom field data migrates into typed custom fields rather than being dropped.

SendCloud webhook endpoint configurations (Parcel status change, shipment event, return update webhooks) are exported as a written inventory document listing each webhook's endpoint URL, event type, and secret key. The webhook subscriptions themselves cannot be transferred to Odoo because they are tied to SendCloud API credentials. The inventory document is delivered to the customer's admin for recreation in Odoo's webhook or automation triggers post-migration.

SendCloud's native shop platform integrations (Shopify, WooCommerce, Magento, PrestaShop, PrestaShop) connect order data to SendCloud. We inventory active integrations and flag which require new API credentials to be generated after migration. Odoo has its own native e-commerce (Odoo Website / eCommerce) and shop connectors, and if the customer intends to consolidate into Odoo's shop platform, we flag the integration migration path in the scope document.

SendCloud user accounts (team members with shipping operation roles) are mapped to Odoo User records by email match. SendCloud role assignments do not have direct Odoo equivalents because Odoo uses a more granular rights group system covering per-app access. We deliver a role mapping table that maps SendCloud user roles to Odoo access groups (Shipping User, Inventory User, Sales User, etc.) for the customer's admin to assign post-migration.

SendCloud shipping label data (PDF, ZPL, PNG formats) is not migrated as binary files. We preserve the label format preferences (format type, carrier-specific formatting) in a written configuration document. After migration, shipping labels are regenerated in Odoo through the delivery carrier integration using the carrier API credentials configured at the destination. This is standard practice because label binary files expire and carrier APIs regenerate current labels on demand.

SendCloud tracks Parcel status transitions (created, label_printed, handed_to_carrier, in_transit, out_for_delivery, delivered, returned) over time. Each status transition timestamp migrates as a note or activity entry on the corresponding Odoo Stock Picking record, preserving the historical delivery timeline. This ensures the full tracking history is available in Odoo without requiring access to the SendCloud dashboard.