Skip to content
Get a quote

SendCloud to Zoho CRM migration

We migrate Address, Parcel, Shipment, and Return records from SendCloud into Zoho CRM, mapping ship-to addresses to Contacts and Accounts, preserving carrier routing and tracking status in custom objects, and flagging the webhook credentials and return portal configurations that require re-establishment after cutover.

Short answer

FlitStack AI migrates contacts, accounts, contact or accounts, custom module: parcels and custom module: shipments from SendCloud to Zoho CRM, 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: 2-4 weeks.

By

Source SendCloud
DestinationZoho CRM
ContactAccountContact or AccountCustom Module: ParcelCustom Module: Shipment
Mapped field by field · sample run · one-click rollback

What moves from SendCloud to Zoho CRM?

SendCloud is a purpose-built e-commerce shipping platform, not a CRM.

Read the full summary

Migrating from SendCloud to Zoho CRM means extracting operational shipping data and embedding it inside a full customer relationship management system. We convert SendCloud's structured address records into Zoho Contacts and Accounts, and we map Parcels, Shipments, and Returns to Zoho custom modules that preserve tracking numbers, carrier routing, and return status. Carrier-specific negotiated rates are stored in SendCloud's internal tables and do not export; we flag this during scoping so customers can plan carrier re-engagement. Return portal settings, webhook subscriptions, and shop platform integration credentials require manual recreation in Zoho based on the exported configuration inventory. Zoho's API credit limits (25,000/day per org or 500/user, whichever is lower) govern our batch sizing during import, and custom field creation costs 10 credits per field, which we factor into the scoping estimate. We do not migrate SendCloud automations or carrier rate tables.

1:1

Address (ship-to) → Contact

SendCloud ship-to addresses stored as structured objects map to Zoho CRM Contacts.

How it maps

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.

1:1

Address (ship-to, business) → Account

Where SendCloud address records include a company name or represent B2B shipments, we map these to Zoho CRM Accounts.

How it maps

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.

configuration

Address (ship-from) → Contact or Account (warehouse)

SendCloud ship-from addresses represent merchant warehouses or 3PL locations.

How it maps

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.

1:1

Parcel → Custom Module: Parcel

SendCloud Parcels migrate to a Zoho custom module named 'Parcel' (API name Parcel__c).

How it maps

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.

1:1

Shipment → Custom Module: Shipment

SendCloud Shipments migrate to a Zoho custom module named 'Shipment' (API name Shipment__c).

How it maps

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.

1:1

Return → Custom Module: Return

SendCloud Returns migrate to a Zoho custom module named 'Return' (API name Return__c).

How it maps

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.

What moves11 objects
SendCloudZoho CRM
  • AddressContact1:1
  • AddressAccount1:1
  • AddressContact or Accounttransformed
  • ParcelCustom Module: Parcel1:1
  • ShipmentCustom Module: Shipment1:1
  • ReturnCustom Module: Return1:1

+ 5 more in the mapping below

How SendCloud and Zoho CRM 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.

DimensionSendCloudZoho CRM
Platform focusE-commerce shipping automation for label creation, tracking, and returnsHorizontal CRM for sales, customer management, and marketing automation
Core data unitParcel, Shipment, Return (shipping operations)Contact, Account, Lead, Opportunity (customer relationships)
Custom objectsAvailable on Growth and above for custom Parcel and Return fieldsAvailable from Standard tier ($14/user/mo) with no setup fee
Pricing modelPer-month subscription scaling with parcel volume and carrier countPer-user with annual discount; free tier supports up to 3 users
Integration modelNative shop platform connectors (Shopify, WooCommerce, Magento)Zoho Marketplace apps and REST API with Deluge scripting
API rate limitsNot publicly documented, making high-volume export scoping unpredictable25,000 requests/day per org or 500/user license; 10 credits per custom field operation
Return portalBranded return portal with configurable reason codes and label templatesZoho Desk return flows require manual configuration as a separate module

What to watch for in a SendCloud to Zoho CRM migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Carrier-specific negotiated rates do not transfer

SendCloud stores each merchant's negotiated carrier rates within its own platform's internal tables.

How we handle it

These rates are not exported as a portable dataset via the SendCloud API or CSV export. We flag this during scoping so customers understand they need to re-negotiate carrier contracts or port existing agreements directly with carriers before or after migration. We preserve all Parcel, Shipment, Return, and label-format data that does not depend on SendCloud's internal rate tables. This gotcha applies to all migrations away from SendCloud, not specifically to Zoho CRM, and is included because it directly impacts the customer's operational continuity.

high

Webhook and integration credentials must be re-established

SendCloud webhook subscriptions and shop platform integration credentials are tied to the SendCloud account and do not carry over to Zoho CRM.

How we handle it

After migration, live webhook connections will not function in Zoho. We export webhook endpoint configurations, event types, and signing secrets in a written inventory that the customer's admin uses to recreate connections in Zoho Deluge or an integration middleware. Shop platform credentials must be rotated and re-registered in both the source (to revoke access) and destination (to establish access) systems to avoid duplicate events or missed tracking updates.

medium

Zoho API credit consumption limits batch sizing

Zoho CRM enforces API credit limits of 25,000 requests per day per organization or 500 requests per user license, whichever is lower.

How we handle it

Custom field creation, updates, and deletions each consume 10 credits per field. For large Parcel and Return migrations, we pre-calculate credit consumption across custom field schema creation and data import batches, and we implement exponential backoff when Zoho returns 429 rate limit responses. We pause and resume import across the rolling 24-hour credit window rather than bypassing limits, because violating rate limits can trigger temporary account restrictions.

medium

Return portal configurations are account-specific and not fully API-accessible

SendCloud's return portal settings, including return reason codes, return label templates, and return-to-address configurations, are set at the account level and are not fully exposed via the public API.

How we handle it

We inventory all available return configuration data during scoping, but the full portal setup cannot be programmatically exported. Customers should plan to manually reconfigure return portal settings in Zoho Desk or via a custom Zoho module post-migration using the exported configuration inventory as a reference.

medium

Zoho custom module creation consumes API credits and requires schema design

Creating Zoho custom modules (Parcel__c, Shipment__c, Return__c) costs 500 API credits per module, and custom field creation costs 10 credits per field.

How we handle it

For migrations with extensive custom field schemas, we pre-create the schema before import begins and batch field creation calls to stay within daily credit limits. We coordinate with the customer's Zoho admin to ensure the migration user has the necessary API permissions and to temporarily disable any validation rules that might block import of shipment data that does not conform to Zoho's standard field constraints.

How the migration runs

  1. Discovery and scoping

    We audit the source SendCloud account across plan tier, Parcel and Return record volume, active carrier integrations, webhook subscriptions, custom field schemas, and return portal configuration.

    What this step covers

    We map these against Zoho CRM editions (Standard at $14/user/mo covers custom modules; no onboarding fee applies) and confirm the custom module names, field types, and lookup relationships needed in Zoho. The discovery output is a written migration scope, a Zoho custom module schema design, and a flag of any carrier rate data or return configurations that will not transfer.

  2. Custom module and schema pre-creation in Zoho Sandbox

    We create the Parcel__c, Shipment__c, and Return__c custom modules in a Zoho Sandbox org, including all custom fields, picklist values, and lookup relationships.

    What this step covers

    We coordinate with the customer's Zoho admin to grant the migration user the necessary API permissions and to temporarily disable validation rules that could block shipment data import. Schema validation in Sandbox precedes any production migration.

  3. Address extraction and Contact-Account disambiguation

    We extract all ship-to addresses from SendCloud Parcels and group them by recipient.

    What this step covers

    Addresses with a company name are routed to Zoho Accounts; individual consumer addresses route to Contacts. Where ambiguity exists (an address could be either a Contact or an Account), we flag the record for the customer's review rather than making a unilateral decision. The Contact and Account import completes before Parcel and Shipment imports because Parcel__c records have a lookup to the recipient Contact.

  4. Parcel and Shipment migration in dependency order

    We run Parcel and Shipment migration in strict dependency order: Shipment records are created first, then Parcel records are linked to the correct Shipment via the shipment lookup field.

    What this step covers

    Each Parcel also links to the recipient Contact and merchant Account via lookup fields resolved at migration time. We use Zoho's bulk API with chunking and implement exponential backoff on 429 responses to stay within the 25,000/day API credit window. Custom fields from SendCloud map to pre-created Zoho custom fields with type matching (text to text, date to date, picklist to picklist).

  5. Return migration with original Parcel linkage

    We migrate Return records after Parcels are imported, linking each Return to its originating Parcel via the Parcel lookup field.

    What this step covers

    Return reason codes, label status, and RMA data populate Zoho custom fields. The return portal configuration inventory is delivered as a written document for manual reconfiguration in Zoho Desk or a custom return module.

  6. Webhook and integration handoff

    We deliver the webhook subscription inventory (endpoint URLs, event types, signing secrets) and the shop platform integration inventory (active connections and required credential rotation steps) as written documents.

    What this step covers

    We do not configure live webhook endpoints or re-register shop platform credentials as part of standard migration scope; these require credential rotation in live systems and are completed by the customer's admin post-migration. We support a one-week post-cutover window for reconciliation of any import discrepancies.

SendCloud Zoho CRM
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Zoho CRMRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

2-4 weeksTypical, smaller accounts
5-8 weeksLarge or heavily customised accounts

Pricing reflects record volume, custom module count, and the degree of custom field and configuration work required. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for SendCloud to Zoho CRM →

Why teams move from SendCloud to Zoho CRM

  • SendCloud is shipping automation software, not a CRM. E-commerce businesses that outgrow shipping-only tools move to Zoho CRM to consolidate customer addresses, shipment history, and return records alongside leads, deals, and support cases in a single platform. Reviewers on comparison sites cite the need for a unified customer view and the absence of contact management, sales pipeline, and marketing features in SendCloud as the primary driver for switching to a horizontal CRM.
  • Zoho CRM Standard starts at $14 per user monthly (annual billing) with a free tier for up to three users, versus SendCloud's Growth plan at €79/mo which adds carriers and customs features but still has no CRM capabilities. Businesses seeking to consolidate shipping cost management with customer relationship management find Zoho's per-user pricing more predictable than SendCloud's volume-based carrier scaling.
  • SendCloud's API rate limits are not publicly documented, which creates scoping uncertainty for high-volume shipment exports. Zoho CRM publishes explicit API credit limits (25,000/day per org or 500/user, whichever is lower), allowing migration engineers to size batches accurately and avoid throttling during import. Migration predictability improves significantly when the destination platform's limits are known upfront.
  • Zoho CRM's custom object support is available from the Standard tier without an onboarding fee, whereas SendCloud's custom field schema for Parcels and Returns is restricted to certain plan tiers. Teams requiring a flexible data model for shipment tracking linked to customer records can achieve this in Zoho without upgrading to SendCloud Enterprise.

Questions, answered

SendCloud to Zoho CRM migration questions

How long does a SendCloud to Zoho CRM migration take?

Straightforward migrations with up to 30,000 Parcel records and no complex address disambiguation land between two and four weeks. Migrations with large address datasets requiring Contact-to-Account disambiguation, multiple custom modules for Parcel and Return objects, or extensive custom field schemas extend to five to eight weeks. The Zoho API credit window (25,000/day per org) governs batch pacing for large record sets and is the primary factor that determines whether a migration lands on the short or long end of the range.

Do SendCloud carrier rates and routing rules migrate to Zoho CRM?

No. SendCloud stores each merchant's negotiated carrier rates within its own platform and does not expose these as exportable data. We map the carrier name and service level to custom fields on the Parcel record, but the actual negotiated rate tables do not transfer. Customers should plan to re-negotiate carrier contracts or port existing agreements directly with carriers. Routing rules are similarly SendCloud-internal; we document the active routing configuration and recommend rebuilding carrier selection logic as Zoho workflow rules post-migration.

Can SendCloud return portal configurations migrate to Zoho?

No. SendCloud's return portal settings, including return reason codes, label templates, and return-to-address configurations, are set at the account level and are not fully accessible via the public API. We export all available return configuration data during scoping and deliver it as a written inventory document for manual reconfiguration in Zoho. Customers should expect to rebuild return portal settings in Zoho Desk or a custom Zoho module post-migration.

Will my SendCloud webhook subscriptions continue working after migration?

No. SendCloud webhook subscriptions are tied to the SendCloud account and cannot be transferred to Zoho CRM. We export the full webhook configuration inventory (endpoint URLs, event types, signing secrets) as a written document. Your admin uses this to recreate webhook subscriptions in Zoho Deluge or a third-party integration tool. Shop platform integration credentials must also be rotated and re-registered in both systems to avoid duplicate events.

Do SendCloud automations and rules migrate to Zoho?

SendCloud does not expose its carrier routing rules or return workflow configurations via a programmable API, so there is no automation logic to migrate. We document the active routing and return portal configurations for your admin to rebuild in Zoho. Zoho workflows, Blueprint stages, and Deluge functions serve as the replacement automation layer; these require manual rebuild post-migration.

What happens to my SendCloud custom fields on Parcels and Returns?

We inventory all SendCloud custom field schemas during scoping and map them to equivalent custom fields on the Parcel__c and Return__c Zoho modules. Custom fields are pre-created before data import begins, with data types matched (text, number, date, picklist). Note that Zoho charges 10 API credits per custom field creation, which we factor into the scoping estimate. Large custom field schemas can extend the preparation phase of the migration timeline.

Can FlitStack AI migrate historical shipment tracking data?

Yes. We migrate full Parcel and Shipment history including tracking numbers, carrier names, service levels, status timestamps, and shipment weights. Tracking histories are preserved as records in the Parcel__c and Shipment__c custom modules. We do not migrate label binary files (PDFs or ZPL files) because these are generated on-demand by carrier APIs. We document the label format preferences for manual reconfiguration in Zoho's label printing setup.

Get a quote

Moving from SendCloud to Zoho CRM?

Tell us roughly how many records and objects you have. We scope the mapping and the Zoho CRM setup with you, then send a quote.

Get a quote