SendCloud to Salesforce migration
We migrate Parcels, Shipments, Returns, and Address records from SendCloud into Salesforce as custom objects linked to Account and Contact context, preserving carrier routing rules, tracking histories, and custom field schemas while flagging the negotiated carrier rate tables and webhook credentials that must be re-established at the destination.
FlitStack AI migrates shipment__cs, return_request__cs, account address fields or shippingaddress__cs, carrier__cs and custom fields on shipment__c and return_request__cs from SendCloud to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from SendCloud to Salesforce?
SendCloud is an e-commerce shipping automation platform; Salesforce is a CRM.
Read the full summary
This migration is not a feature-for-feature replacement — it is a data-preservation operation that moves historical shipping data into Salesforce so that order fulfillment context lives alongside customer and account records. We map SendCloud Parcels and Shipments to a Shipment__c custom object, Returns to a Return__c custom object, and Address records to a ShippingAddress__c object or Account Address fields, all linked to the parent Account and Contact via Lookups. SendCloud's carrier-specific negotiated rate tables do not export as portable data; we flag this during scoping so customers understand they will need to re-negotiate or port carrier contracts directly. Webhook endpoint configurations, shop platform integration credentials, and return portal settings are inventoried and documented for manual rebuild. Workflows, shipping automation rules, and branded tracking page configurations are not migratable and are delivered as a written inventory for the customer to configure in Salesforce or a replacement shipping platform.
Parcel → Shipment__c (custom object)
SendCloud Parcel records map to a Salesforce custom object Shipment__c with fields for Parcel ID, weight, dimensions, reference number, status, and carrier routing.
How it maps
The Parcel's status field maps to a custom Shipment_Status__c picklist. Shipment__c is linked to the parent Account via a Lookup relationship, allowing fulfillment context to appear on the Account record. The original SendCloud Parcel ID is preserved in a custom field sc_parcel_id__c for audit traceability.
Shipment → Shipment__c (parent grouping)
SendCloud Shipment records (logical groupings of one or more Parcels to the same recipient) map to a parent Shipment__c record that aggregates child Parcel records via a lookup relationship.
How it maps
The Shipment's destination Address, shipping method, service level, and estimated delivery date become fields on the parent Shipment__c. If the destination Salesforce org uses Order Management, the Shipment__c can alternatively be linked to an Order record via WhatId.
Return → Return_Request__c (custom object)
SendCloud Return records map to a custom object Return_Request__c with fields for RMA number, return reason code, return label tracking number, and RMA status.
How it maps
The original SendCloud return reason codes are mapped to a picklist or multi-select picklist in Salesforce. Return_Request__c is linked to the original Shipment__c record (via lookup) and to the parent Account and Contact for service context.
Address (ship-to, ship-from) → Account Address fields or ShippingAddress__c
Ship-from and ship-to addresses from SendCloud Shipments migrate as structured address records.
How it maps
In Salesforce, we map addresses to Account ShippingAddress fields for the merchant's ship-from location, and to a custom ShippingAddress__c object linked to Account or Contact for recipient addresses. Address validation rules differ between platforms; we flag address format discrepancies during reconciliation and apply normalization where possible.
Carrier → Carrier__c (custom object)
SendCloud carrier configurations map to a Carrier__c custom object with fields for carrier name, carrier code, and service levels.
How it maps
We map carrier-to-carrier between SendCloud and Salesforce or the customer's preferred carrier integration. Merchant-specific negotiated carrier rates are SendCloud-stored values and do not transfer; we document the carrier mapping and flag that rate renegotiation or direct carrier account porting is required separately.
Custom Fields (Parcels, Returns) → Custom fields on Shipment__c and Return_Request__c
Custom fields added to SendCloud Parcels and Returns on Growth and above plans are inventoried during scoping.
How it maps
Each custom field is mapped to an equivalent custom property on the corresponding Salesforce custom object, with Salesforce field types selected to match the source data type (text, number, date, picklist). The custom field schema is pre-created in the destination org before data import begins.
- ParcelShipment__c1:1
- ShipmentShipment__c1:1
- ReturnReturn_Request__c1:1
- AddressAccount Address fields or ShippingAddress__ctransformed
- CarrierCarrier__ctransformed
- Custom FieldsCustom fields on Shipment__c and Return_Request__ctransformed
+ 6 more in the mapping below
How SendCloud and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | SendCloud | Salesforce |
|---|---|---|
| Platform purpose | E-commerce shipping automation (labels, tracking, returns across 80+ carriers) | CRM for sales, service, and customer relationship management |
| Record model | Parcels and Shipments as transactional shipping units with carrier routing | Standard objects (Account, Contact, Opportunity, Case) plus custom objects for shipping context |
| Custom objects | Custom fields on Parcels and Returns available on Growth and above | Custom objects available from Professional tier without setup fees |
| Pricing model | Monthly subscription per tier (€26-€155/mo) plus per-parcel volume | Per-user per month at edition tier ($80-$330/user/mo) |
| Automation | Shipping automation rules and carrier routing rules in-platform | Salesforce Flow for record-triggered, scheduled, and screen automations |
| Integrations | Native shop platform integrations (Shopify, WooCommerce, Magento) | AppExchange with 9,000+ listings plus native Salesforce integrations |
| Return handling | Return portal with reason codes, label templates, return-to-address settings | Case management with custom Return Request object and email templates |
What to watch for in a SendCloud to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Negotiated carrier rates are SendCloud-stored values that do not export
SendCloud stores each merchant's negotiated carrier rates within its own platform tables.
How we handle it
These rates are not exposed via the public API and cannot be exported as a portable data set. When migrating away from SendCloud, customers will need to re-negotiate carrier contracts or port existing agreements directly with carriers. We flag this during scoping so customers understand the rate data gap. We preserve all Parcel, Shipment, Return, tracking history, and label-format data that does not depend on SendCloud's internal rate tables.
Webhook subscriptions and integration credentials must be manually rebuilt
SendCloud webhook subscriptions, shop platform integrations, and carrier API credentials are tied to the SendCloud account.
How we handle it
After migration, the destination platform will not inherit these live connections. We export webhook endpoint configurations and integration settings as a structured inventory document so they can be recreated, but actual credential rotation and endpoint updates must be completed in both the source and destination systems. Skipping this step results in duplicate events or missed tracking updates during the cutover window.
SendCloud is a shipping platform, not a CRM — there is no feature parity migration
SendCloud and Salesforce serve fundamentally different purposes.
How we handle it
SendCloud manages e-commerce shipping workflows (label generation, carrier routing, tracking, returns); Salesforce manages customer relationships (accounts, contacts, opportunities, cases). Migrating from SendCloud to Salesforce does not replace shipping functionality — it embeds historical shipping data as context within a CRM. Customers must select a replacement shipping platform (such as ShipStation, EasyShip, or a direct carrier integration) to maintain active label generation and tracking after SendCloud is decommissioned.
Return portal settings are account-specific and not exposed via the API
SendCloud's return portal configuration includes return reason codes, return label templates, and return-to-address settings set at the account level.
How we handle it
These are not fully exposed via the public API. We inventory available return configuration during scoping and document the settings in the migration deliverable. Customers should plan for manual reconfiguration of return portal settings in the replacement shipping platform and may need to recreate return reason code picklists in Salesforce if the Return_Request__c custom object uses a controlled vocabulary.
Free plan parcel cap can be exceeded during migration export
SendCloud's free plan allows up to 20 parcels per month.
How we handle it
Migration export operations that pull historical shipment data consume API calls against this limit, potentially causing the account to hit its cap before the migration is complete. We scope the account's current plan before beginning export and recommend customers temporarily upgrade to a paid tier (Lite at €26/mo or above) if historical volume exceeds 20 parcels during the export window.
How the migration runs
Discovery and scoping
We audit the SendCloud account across plan tier (Free/Lite/Growth/Premium/Enterprise), parcel volume, shipment count, return history, active carrier integrations, webhook subscriptions, custom field schemas on Parcels and Returns, and return portal configuration.
What this step covers
We pair this with a review of the destination Salesforce org's existing data model to determine whether a Shipment__c / Return_Request__c custom object structure is sufficient or whether shipping data should be linked to existing Order or Case objects. The discovery output is a written migration scope, a custom object schema design, and a list of items requiring manual reconnection post-migration.
Custom object schema design
We design the destination schema in Salesforce.
What this step covers
This includes provisioning Shipment__c, Return_Request__c, Carrier__c, Shipment_Event__c, and any other custom objects identified during discovery. We configure custom fields with Salesforce types mapped from SendCloud field types, establish Lookup relationships to Account and Contact, and define picklist values for Shipment_Status__c, Return_Reason__c, and Carrier__c. Page Layouts are assigned per profile. Schema is deployed into a Salesforce Sandbox first for validation before production migration begins.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox (Full Copy or Partial Copy) using production-like data volume.
What this step covers
The customer's operations or RevOps lead reconciles record counts (Shipments in, Returns in, Tracking events in), spot-checks 25-50 random Shipment__c records against the SendCloud source, and validates that parent Account lookups resolve correctly. The customer signs off on the schema, mapping, and custom field labels before production migration begins. Any mapping corrections happen here.
Integration inventory and webhook documentation
We export all active SendCloud webhook endpoint configurations, shop platform integration credentials, and carrier API settings as a structured inventory document.
What this step covers
This document lists each integration's endpoint URL, event types, authentication method, and recommended reconnection steps in the replacement shipping platform or Salesforce-based integration. We deliver the inventory to the customer's technical team as a checklist for manual reconnection after cutover.
Production migration in dependency order
We run production migration in record-dependency order: Carrier__c records first (no dependencies), then Account ShippingAddress data, then Shipment__c records with Parcel details and Shipment_Event__c child records (via Bulk API 2.0 for large tracking histories), then Return_Request__c records linked to parent Shipment__c and Account.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. We use Bulk API 2.0 with batch chunking and exponential backoff for tracking event volumes over 50,000 records.
Cutover, validation, and integration rebuild handoff
We freeze SendCloud writes during cutover, run a final delta migration of any records modified during the migration window, then mark Salesforce as the system of record for migrated shipping context.
What this step covers
We deliver the webhook and integration inventory document to the customer's technical team with a recommended rebuild sequence. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild SendCloud shipping automation rules in Salesforce or a replacement shipping platform; that is a separate engagement or an internal technical task.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom object complexity, and integration reconnection scope. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for SendCloud to Salesforce →Why teams move from SendCloud to Salesforce
- SendCloud is purpose-built for shipping automation and lacks the broader CRM, sales pipeline, and customer management features that horizontal CRM platforms provide. Teams that start with SendCloud for fulfillment often find they need Salesforce for account management, opportunity tracking, and service case handling, and they consolidate shipping data into Salesforce as a unified customer record context rather than maintaining two disconnected platforms.
- SendCloud's pricing scales with shipment volume and carrier count, making costs harder to predict as order volumes grow. Salesforce's per-user model is more predictable for operations teams that have already committed to a CRM and want shipping context embedded in the customer record without a separate platform subscription.
- Initial SendCloud integration and API setup is complex; customer reviews report needing to assist SendCloud's own development team with incomplete API documentation. Teams with mature Salesforce implementations cite consolidation into a single platform as a reason to move shipping data into Salesforce rather than maintaining a separate integration layer with its own support burden.
- Carrier coverage is inconsistent across certain regions and shipping corridors in SendCloud. Teams shipping internationally with complex customs requirements report limited carrier options, which drives them toward shipping platforms with deeper regional carrier support or toward custom Salesforce integrations with preferred carriers directly.
- Return workflow configurations in SendCloud are account-specific and not exposed in full via the public API. Teams with established return portal settings find that the configuration effort required to rebuild these in a new shipping platform (or in Salesforce with a custom Return Request object) is comparable to the effort of a migration, making it a natural inflection point to evaluate consolidating into Salesforce as the system of record for customer-facing shipping context.
Questions, answered
SendCloud to Salesforce migration questions
How long does a SendCloud to Salesforce migration take?
Most migrations land between three and five weeks for accounts under 50,000 Parcels and 10,000 Returns with a simple Account-linked custom object structure. Migrations with large tracking history volumes (over 100,000 shipment status events), complex custom field schemas, multi-warehouse routing data, or extensive integration reconnection work move to eight to twelve weeks because of custom object schema design, Bulk API time, and integration documentation scope.
Does SendCloud shipping automation migrate to Salesforce Flow?
No. SendCloud shipping automation rules (carrier routing logic, weight-based service selection, automated label selection) are platform-specific and do not transfer to Salesforce. We do not migrate them as code. We deliver a written inventory of active shipping automation rules with their trigger conditions, routing logic, and carrier assignments so the customer's technical team can rebuild them in the replacement shipping platform or evaluate whether Salesforce Flow is an appropriate alternative for any CRM-context automation. Return portal configurations similarly do not migrate; they are documented for manual rebuild.
Will we lose our carrier negotiated rates when we leave SendCloud?
Yes. SendCloud stores each merchant's negotiated carrier rates within its own platform tables, and these rates are not accessible via the public API. When you migrate away from SendCloud, those rates do not export as a portable data set. You will need to re-negotiate carrier contracts or port existing agreements directly with your carriers. We document the carrier-to-carrier mapping during migration so that the replacement shipping platform can be configured with the same carrier connections, but the rate data must be renegotiated separately.
Can we keep SendCloud for shipping and migrate only the data to Salesforce?
Yes. A common pattern is running SendCloud and Salesforce in parallel during a transition period, where SendCloud continues handling active label generation and tracking while shipping history is migrated into Salesforce as a customer context layer. We can perform a partial migration that moves only historical data (Parcels, Shipments, Returns, Addresses, tracking history) into Salesforce custom objects, leaving SendCloud operational until a replacement shipping platform is fully configured. This requires coordination on the webhook reconnection sequence to avoid duplicate tracking events.
What happens to our shop platform integrations (Shopify, WooCommerce, Magento)?
SendCloud shop platform integrations (Shopify, WooCommerce, Magento, PrestaShop) are tied to the SendCloud account and cannot be transferred to Salesforce. We inventory all active integrations during scoping, documenting the current API credentials, webhook endpoints, and data sync scope. The customer's technical team uses this inventory to reconfigure integrations with the replacement shipping platform or to establish new Salesforce-to-shop-platform connections if order-to-shipment data should flow through Salesforce.
Do we migrate tracking history into Salesforce?
Yes. We migrate the full SendCloud tracking history as Shipment_Event__c child records under the parent Shipment__c. Each event carries the timestamp, status, location, and carrier scan description. The tracking timeline appears as a related list on the Shipment__c record, allowing service and ops teams to view delivery history directly in Salesforce. We use the Salesforce Bulk API 2.0 for tracking event volumes over 50,000 records to ensure reliable batch processing.
Can FlitStack AI also help select and set up the replacement shipping platform?
No. FlitStack AI specializes in data migration between platforms, not in shipping platform selection or setup. We do not recommend, implement, or configure replacement shipping platforms such as ShipStation, EasyShip, Shipbob, or direct carrier portals. We can document the integration and automation requirements from your SendCloud account so that your technical team or a shipping platform implementation partner has a complete specification for the replacement setup. We can, however, migrate data into any shipping platform that exposes a documented API or supports CSV import, as a separate engagement.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → AutoText to SalesforceMapping · history · rollbackSpotler CRM to SalesforceMapping · history · rollbackHighLevel to SalesforceMapping · history · rollbackOdoo CRM to SalesforceMapping · history · rollbackDubsado to SalesforceMapping · history · rollbackClio to SalesforceMapping · history · rollback SendCloud to HubSpotMapping · history · rollbackSendCloud to Zoho CRMMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from SendCloud to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote