Migrate from SendCloud to Zoho CRM

SendCloud ship-to addresses stored as structured objects map to Zoho CRM Contacts. We extract recipient name, street address, city, state/province, postal code, and country, and map these to the standard Contact fields. Email and phone fields are populated where available in the address record or linked Parcel data. Address is the parent of any Contact import so that the Account link can be resolved for records that represent business accounts rather than individual recipients.

Where SendCloud address records include a company name or represent B2B shipments, we map these to Zoho CRM Accounts. We use the company name as the Account Name and populate the billing address fields. Individual consumer addresses without a company field remain as Contacts without an Account parent.

SendCloud ship-from addresses represent merchant warehouses or 3PL locations. We map these to Contacts marked with a Role custom field (e.g., 'Warehouse' or 'Ship-From') or to an Account named after the warehouse location, depending on the customer's preference. The customer's Zoho admin chooses the strategy during scoping.

SendCloud Parcels migrate to a Zoho custom module named 'Parcel' (API name Parcel__c). We map Parcel ID, reference number, weight, dimensions, status, carrier, service level, and the create timestamp to custom fields on the module. Parcel is the child of the Contact (recipient) and Account (merchant) via lookup relationships we configure before import. Custom fields on SendCloud Parcels (Growth and above) map to additional custom fields on Parcel__c.

SendCloud Shipments migrate to a Zoho custom module named 'Shipment' (API name Shipment__c). A Shipment groups one or more Parcels sent to the same recipient, so we create the Shipment record first and link each child Parcel record via a lookup field. We map shipment ID, destination address (linked to the Contact), shipping method, service level, estimated delivery date, and shipment status. Shipment__c is lookup-linked to the Contact (recipient) and Account (merchant) before Parcel import begins.

SendCloud Returns migrate to a Zoho custom module named 'Return' (API name Return__c). We map return ID, return reason code, carrier, return label status, RMA number, and return create date. The Return record links to the original Parcel via a lookup field and to the Contact that initiated the return. Return portal settings (reason codes, label templates, return-to-address) are not exposed via the SendCloud API and cannot be programmatically migrated; we export available configurations for manual reconfiguration in Zoho.

SendCloud carrier routing rules define default carrier selection per shipment corridor. We map the selected carrier and service level to custom picklist fields on Parcel__c rather than creating a separate module, because routing rules are configuration not transactional data. The customer should plan to rebuild carrier selection logic as Zoho workflow rules or Blueprint stages post-migration.

SendCloud supports custom fields on Parcel and Return objects on Growth and above plans. We inventory all custom field schemas during scoping, map each to an equivalent Zoho custom field (with matching data type, picklist values, and required/optional status), and pre-create the schema in Zoho before data import. Custom field creation costs 10 API credits per field in Zoho, which we factor into our scoping estimate.

SendCloud webhook subscriptions for Parcel status changes, shipment events, and return updates are tied to the SendCloud account and do not migrate to Zoho. We export the webhook endpoint URLs, event types, and signing secrets as a configuration inventory document. The customer's admin uses this to recreate webhook subscriptions in Zoho Deluge or via a third-party middleware tool post-migration. We do not configure live webhook endpoints as part of standard migration scope.

SendCloud's native integrations with Shopify, WooCommerce, Magento, PrestaShop, and other shop platforms connect order data to shipping labels. We inventory active integrations and flag which require new API credentials to be generated and registered at the destination. The customer completes integration re-registration post-migration; we do not perform this step as it involves credential rotation in live shop systems.

SendCloud user accounts with team role assignments are mapped to Zoho Contacts with a Role custom field. We preserve user name, email, and team assignment for audit purposes. Zoho's native user management (Users module) is not populated from SendCloud because Zoho Users must be licensed and provisioned within Zoho's own identity system, which is a separate administrative step.