Migrate from SendCloud to Freshsales

SendCloud stores ship-to and ship-from addresses as structured objects linked to Shipments and Returns. Each unique address becomes a Freshsales Contact with the recipient or sender name, email (if present), phone (if present), and full postal address mapped to Freshsales standard fields. We deduplicate addresses by normalized street address string before import to avoid creating duplicate Contact records for repeat customers. The first Contact from an address set gets the Account created; subsequent shipments to the same normalized address link to the existing Account via the primary address match.

SendCloud Shipment records contain tracking number, carrier name, shipping method, service level, estimated delivery date, and status. We attach these as structured Note records to the parent Contact using the address match. Each Note contains the tracking URL (carrier tracking page), shipment reference, and status so the Freshsales user has shipping context without a live SendCloud connection. We do not create Freshsales Deal records from shipping data because a Shipment does not imply a sales opportunity; the customer creates Deals from their own sales process.

SendCloud Parcel records carry reference number, weight, dimensions, and status. The parcel reference number maps to a Freshsales custom text field on Contact (e.g., last_parcel_reference__c). Weight and dimensions map to custom number fields if the customer requires shipping preference context on the Contact record. We inventory all custom field schemas during scoping and pre-create the equivalent custom fields in Freshsales before migration.

SendCloud Return records track the inbound flow of parcels back to the merchant, including RMA number, return reason code, return label status, and resolution. We map Returns to Freshsales Tasks attached to the Contact with Subject = Return: [RMA number], Status, Priority (set to High for unresolved returns), and description containing the return reason and resolution. Closed returns map to completed Tasks; open returns map to open Tasks requiring follow-up.

SendCloud carrier names (DHL, UPS, FedEx, and 80+ others) have no native equivalent in Freshsales. We map carrier names to a custom picklist field on Contact (preferred_carrier__c) for quick reference, or embed the carrier name in the shipment Note. We do not create a separate Carrier object in Freshsales because Freshsales does not have a native carrier or logistics object type.

SendCloud webhooks notify external systems of parcel status changes, shipment events, and return updates. These subscriptions are tied to the SendCloud account URL and credentials and have no Freshsales equivalent in the standard CRM data model. We export the complete list of active webhook endpoint URLs, event types, and payload configurations so the customer's admin can recreate them in their preferred notification system (Freshsales Workflows, a middleware like Zapier, or a custom endpoint) post-migration.

SendCloud integrations with Shopify, WooCommerce, Magento, PrestaShop, and other shop platforms connect order data to the shipping workflow. These integrations are not transferable to Freshsales. We inventory all active integrations, the credentials or API keys in use, and the event-mapping configuration so the customer's admin can set up Freshsales shop integration (if available) or a middleware connection during the post-migration stabilization window.

SendCloud user accounts with shipping operations roles (label creator, returns handler, admin) are mapped to Freshsales User records by email match. Permission structures (admin vs. standard user) map to Freshsales role assignments. Note that SendCloud user permissions govern shipping operations (which carriers a user can access, which warehouses they can ship from) and do not have a direct Freshsales equivalent; these are reconfigured manually post-migration based on the Freshsales role hierarchy.