Migrate from SendCloud to HighLevel

SendCloud ship-to and ship-from addresses stored as structured objects linked to Shipments and Returns map to GoHighLevel Contact records. The Contact's address fields (street, city, state/province, postal_code, country) are populated directly. We preserve the address type designation (shipping vs billing) as a custom Contact field for use in GoHighLevel Workflows and personalization. Address dedupe is performed by email address + postal code combination to avoid creating duplicate Contacts for repeat customers.

SendCloud Parcels and Shipments do not store a separate Customer object; the recipient data lives on the Parcel record. We extract name, email, phone (if present), and address from Parcel records and create or match GoHighLevel Contacts. Where the same email appears across multiple Parcels, we update the existing Contact rather than creating duplicates. Phone numbers present a known limitation: SendCloud does not consistently populate phone on Parcel records, so contacts without a phone number on the source side will not have one at the destination.

Each SendCloud Parcel record carries weight, dimensions, reference number, status, carrier, service level, and tracking number. We create a GoHighLevel Custom Object named Parcel_History with fields for tracking_number, carrier, status, service_level, weight_kg, reference, shipped_date, and delivery_date. Each Parcel becomes one Custom Object record linked via a Contact Lookup to the recipient Contact. The migration preserves the full status history as a JSON-serialized field or as individual Custom Object records per status event depending on the customer's reporting requirements. Note that SendCloud's carrier-specific rate data is stored in SendCloud's own internal tables and is not exported; we flag this during scoping so the customer understands rate history will not appear at the destination.

SendCloud Return records track return reason codes, RMA status, return label generation, and resolution. We create a GoHighLevel Custom Object named Return_Request with fields for rma_number, reason_code, status, return_label_url (stored as text, not as a file), initiated_date, and resolution. Each Return links via a Contact Lookup to the original customer Contact and via a Parcel_History Lookup to the original shipment. Return portal configuration settings (custom reason codes, label templates, return-to-address settings) are not exposed via the SendCloud API in full; we inventory what is available and document the manual reconfiguration required in GoHighLevel Workflows for return handling.

SendCloud label files (PDF or ZPL binary output per Parcel) are generated on-demand via carrier API calls and are not stored as persistent exported artifacts in SendCloud's API. We do not migrate label binary files. Instead, we document each Parcel's label format preference (carrier, size, layout) as a field on the Parcel_History Custom Object record so that the customer can re-generate labels using their preferred label printing tool or integration at the destination. The customer should plan to connect a label printing integration (such as a carrier-native plugin or a third-party tool like Shippo or EasyShip) inside GoHighLevel's workflow layer post-migration.

SendCloud webhook endpoint configurations (Parcel status change URLs, shipment event endpoints, return update hooks) are tied to the SendCloud account and cannot be transferred. We export the webhook endpoint URLs, event types, and payload configurations during scoping so the customer has a written record. The customer recreates these triggers as GoHighLevel Workflows or uses GoHighLevel's inbound webhook trigger to receive status events from SendCloud if SendCloud is retained as the shipping layer. If SendCloud is fully decommissioned, the customer connects a replacement shipping platform (such as Shippo, Packi, or a carrier direct integration) that posts tracking events to GoHighLevel via its webhook API.

SendCloud's native integrations with Shopify, WooCommerce, Magento, PrestaShop, and 50+ shop platforms connect order data to SendCloud for label creation. We inventory all active shop platform integrations during scoping. At the destination, GoHighLevel's native integrations with Shopify, WooCommerce, and Wix connect the shop order data directly to GoHighLevel Contacts, Opportunities, and Custom Objects. The customer rotates API credentials and reconnects the shop integration in GoHighLevel. We do not perform the credential rotation; we document the required steps and the customer's admin completes them.

SendCloud User accounts include role assignments tied to shipping operations. We extract the user list with email addresses and role names. Users are matched by email to existing GoHighLevel User accounts. Any SendCloud user without a matching GoHighLevel User is added to a reconciliation list for the customer's admin to provision. SendCloud permission structures (admin, manager, shipper roles) are platform-specific and do not transfer; GoHighLevel's own role and permission model requires manual configuration.