---
title: "SendCloud to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate SendCloud to HubSpot with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/sendcloud/to/hubspot"
---

# SendCloud to HubSpot migration

Moving from SendCloud shipping automation to HubSpot CRM means bringing your logistics data into a customer-centric platform for the first time. FlitStack AI maps SendCloud shipment records, addresses, carrier information, and return requests into HubSpot contacts, companies, and custom objects — preserving original shipment timestamps and linking every record to the correct HubSpot owner by email match.

Short answer

FlitStack AI migrates contact + company properties, custom object: shipments, custom shipment object — event\_log properties, custom object: return requests and hubspot users from SendCloud to HubSpot, 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: 72–96 hours for under 50,000 SendCloud shipment records.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/sendcloud/to/hubspot#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source SendCloud ![](https://flitstack.ai/platforms-trim/sendcloud.webp)

Destination HubSpot ![](https://flitstack.ai/platforms-trim/hubspot.webp)

Contact + Company properties Custom Object: Shipment Custom Shipment object — event\_log property Custom Object: Return Request HubSpot User

Mapped field by field · sample run · one-click rollback

## What moves from SendCloud to HubSpot?

SendCloud is an e-commerce shipping platform that tracks parcels, manages return requests, and automates label generation across carriers.

Read the full summary

It does not function as a CRM — contacts and companies are not its primary objects. HubSpot CRM stores contacts, companies, deals, and tickets, but has no native shipment or order object for logistics data. The migration therefore requires translating SendCloud's shipment-centric data model into HubSpot's contact-centric model: addresses become contact and company properties, shipment records and tracking events become a HubSpot custom object, and carrier/service data becomes custom fields. FlitStack AI reads SendCloud via its REST API (parcels, shipments, return requests, addresses, carrier configurations) and maps every entity to the equivalent HubSpot object or custom object before writing. Original create and update timestamps are preserved as HubSpot custom datetime fields since HubSpot's native CreatedDate and LastModifiedDate are set at migration time. SendCloud workflows — carrier routing rules, return-flow automations, label-print triggers — have no HubSpot equivalent and must be rebuilt using HubSpot workflow tools, which FlitStack documents as part of the rebuild reference package.

merged

### Address (Sender / Recipient) → Contact + Company properties

SendCloud stores sender and recipient addresses per shipment.

How it maps

The recipient address maps to HubSpot contact address properties (street, city, postal\_code, country). The sender address maps to Company address properties if the sender is a business, or to a custom Contact property if it represents a recurring warehouse location.

custom\_field\_required

### Shipment / Parcel → Custom Object: Shipment

SendCloud shipments have no direct HubSpot equivalent.

How it maps

FlitStack creates a HubSpot custom object named 'Shipment' (or your preferred label) with custom properties for carrier, service level, status, weight, shipping rate, label URL, and external SendCloud shipment ID. Each shipment is associated to the HubSpot Contact that matches the recipient email.

transformed

### ShipmentEvent (tracking history) → Custom Shipment object — event\_log property

SendCloud tracking events (carrier scan timestamps, status codes, location) are serialized as a JSON-structured text log in a HubSpot custom long-text property called Event\_Log\_\_c.

How it maps

Original event timestamps are preserved in the serialized structure. HubSpot's timeline does not natively support logistics tracking events, so the serialized log preserves full history without schema changes.

custom\_field\_required

### ReturnRequest → Custom Object: Return Request

ReturnRequest is a distinct SendCloud object with status, reason codes, and a link to the original Shipment ID.

How it maps

We create a HubSpot custom object with fields for return status, return reason, original SendCloud shipment ID, and return tracking number. The object is associated to both the Contact and the original Shipment custom object.

transformed

### SendCloud User / Account → HubSpot User (owner)

SendCloud platform users are matched to HubSpot users by email address.

How it maps

Unmatched SendCloud users are flagged before migration — you can invite them to HubSpot or reassign their records to a fallback owner. No record lands in HubSpot without a resolved owner.

merged

### E-commerce store / platform connection → HubSpot Company

SendCloud stores e-commerce platform credentials (Shopify store, WooCommerce site) per account.

How it maps

These are mapped to HubSpot Company records with the platform name as a custom property. Multiple SendCloud store connections for one business map to one HubSpot Company with multiple platform properties.

******What moves 10 objects

SendCloud HubSpot

- Address Contact merged
- Shipment Custom Object: Shipment transformed
- ShipmentEvent Custom Shipment object — event\_log property transformed
- ReturnRequest Custom Object: Return Request transformed
- SendCloud User HubSpot User transformed
- E-commerce store HubSpot Company merged

\+ 4 more in the mapping below

## How SendCloud and HubSpot 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                                                                                                                                                          | HubSpot                                                                                                                                                              |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Primary object model     | SendCloud is shipment-centric: Parcel, Shipment, ReturnRequest, and Address are the core objects. Contacts exist only as address endpoints.                        | HubSpot is contact-centric: Contact, Company, Deal, and Ticket are the primary objects. No native shipment or logistics object exists.                               |
| Custom objects           | SendCloud supports custom fields on shipments and return requests, stored as key-value pairs per parcel record.                                                    | HubSpot supports custom objects (Enterprise tiers) mapped as independent object types with their own properties and association labels.                              |
| Workflows / automations  | SendCloud carrier routing rules, return-flow triggers, and label-print automations live in SendCloud settings and cannot be exported as transferable logic.        | HubSpot workflows operate on CRM events (property changes, form submissions, deal stage updates) — fundamentally different trigger model from logistics automations. |
| Tracking and events      | SendCloud stores per-shipment event logs: carrier pickup, in-transit scans, delivery confirmation, return initiation. Timestamps are precise to the carrier event. | HubSpot has no native tracking timeline. Tracking history migrates as a custom long-text field on the custom Shipment object, or as activity notes on the contact.   |
| Return requests          | SendCloud has a dedicated ReturnRequest object with status, reason codes, and linked original shipment ID.                                                         | HubSpot has no return-request object. Return data migrates to a custom object or ticket, with original SendCloud shipment ID preserved for reference.                |
| Carrier and service data | SendCloud tracks carrier name, service level, shipping rate, and label URL per shipment. This is structured carrier metadata.                                      | HubSpot has no carrier or shipping-rate field. Carrier name and service level become HubSpot custom properties on the custom Shipment object.                        |
| User / owner model       | SendCloud user accounts are tied to platform access, not contact ownership. API keys are the primary integration credential.                                       | HubSpot requires a named HubSpot user as the record owner. SendCloud platform users are matched to HubSpot users by email for owner assignment.                      |

## SendCloud to HubSpot field mapping

The 27 most-used fields of 27 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/sendcloud/to/hubspot.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

SendCloud HubSpot

1. `contact_name` Address `firstname` Contact
2. `contact_company` Address `company` Contact
3. `email` Address `email` Contact
4. `phone` Address `phone` Contact
5. `street` Address `address` Contact

| SendCloud field                             | HubSpot field                                  | Mapping                 | Note                                                                                                                                                                                                            |
| ------------------------------------------- | ---------------------------------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Address.contact_name`                      | `Contact.firstname`                            | direct                  |                                                                                                                                                                                                                 |
| `Address.contact_company`                   | `Contact.company`                              | direct                  |                                                                                                                                                                                                                 |
| `Address.email`                             | `Contact.email`                                | direct                  |                                                                                                                                                                                                                 |
| `Address.phone`                             | `Contact.phone`                                | direct                  |                                                                                                                                                                                                                 |
| `Address.street`                            | `Contact.address`                              | direct                  |                                                                                                                                                                                                                 |
| `Address.city`                              | `Contact.city`                                 | direct                  |                                                                                                                                                                                                                 |
| `Address.postal_code`                       | `Contact.zip`                                  | direct                  |                                                                                                                                                                                                                 |
| `Address.country`                           | `Contact.country`                              | direct                  |                                                                                                                                                                                                                 |
| `Address.company_name`                      | `Company.name`                                 | direct                  |                                                                                                                                                                                                                 |
| `Address.company_website`                   | `Company.domain`                               | direct                  |                                                                                                                                                                                                                 |
| `Shipment.sendcloud_id`                     | `Custom Shipment.sendcloud_id__c`              | custom\_field\_required | HubSpot custom object property storing the SendCloud internal shipment ID for traceability and delta-run de-duplication.                                                                                        |
| `Shipment.status`                           | `Custom Shipment.shipment_status__c`           | value\_mapping          | SendCloud status values (delivered, in\_transit, returned, error) map to HubSpot custom pick-list values. Unknown or carrier-specific statuses default to a custom 'Other' value.                               |
| `Shipment.carrier`                          | `Custom Shipment.carrier__c`                   | custom\_field\_required | Carrier name from SendCloud stored as a HubSpot custom text property on the Shipment object.                                                                                                                    |
| `Shipment.service`                          | `Custom Shipment.service_level__c`             | custom\_field\_required | SendCloud shipping service level (e.g., standard, express, overnight) stored as a custom pick-list property.                                                                                                    |
| `Shipment.shipping_rate`                    | `Custom Shipment.shipping_rate__c`             | custom\_field\_required | Shipping cost from SendCloud stored as a HubSpot custom currency or number field on the Shipment object.                                                                                                        |
| `Shipment.weight`                           | `Custom Shipment.parcel_weight__c`             | custom\_field\_required | Parcel weight migrated to a custom number field (unit configurable: kg or lbs based on SendCloud account settings).                                                                                             |
| `Shipment.label_url`                        | `Custom Shipment.label_url__c`                 | custom\_field\_required | SendCloud label PDF URL stored as a custom URL property. The file is re-downloaded and re-hosted as a HubSpot file at migration time.                                                                           |
| `Shipment.created_at`                       | `Custom Shipment.original_create_date__c`      | custom\_field\_required | HubSpot's CreatedDate is set at migration time. Original SendCloud shipment creation timestamp preserved as a custom datetime field.                                                                            |
| `Shipment.updated_at`                       | `Custom Shipment.original_update_date__c`      | custom\_field\_required | HubSpot's LastModifiedDate is set at migration time. Original SendCloud last-update timestamp preserved as a custom datetime field.                                                                             |
| `ShipmentEvent.event_timestamp`             | `Custom Shipment.event_log__c`                 | transformed             | All tracking events (carrier scans, delivery confirmations, return initiations) serialized as a JSON array in HubSpot's long-text Event\_Log\_\_c field, preserving original event timestamps and status codes. |
| `ReturnRequest.sendcloud_return_id`         | `Custom Return Request.sendcloud_return_id__c` | custom\_field\_required | Return request ID from SendCloud stored on the HubSpot Return Request custom object for traceability.                                                                                                           |
| `ReturnRequest.status`                      | `Custom Return Request.return_status__c`       | value\_mapping          | SendCloud return status values mapped to HubSpot custom pick-list values. Carrier-returned statuses map to HubSpot equivalents.                                                                                 |
| `ReturnRequest.reason`                      | `Custom Return Request.return_reason__c`       | custom\_field\_required | Return reason code from SendCloud stored as a custom pick-list property. Custom reason codes require value-mapping setup.                                                                                       |
| `ReturnRequest.original_shipment_id`        | `Custom Return Request.original_shipment__c`   | transformed             | Links the Return Request custom object to the original SendCloud shipment by matching the original\_shipment\_id to the sendcloud\_id\_\_c on the Shipment object.                                              |
| `SendCloud User.email`                      | `HubSpot User.email (owner lookup)`            | transformed             | SendCloud user email matched against HubSpot user email for owner assignment. Unmatched users flagged before migration.                                                                                         |
| `E-commerce Store Connection.platform_name` | `Company.platform_source__c`                   | custom\_field\_required | SendCloud store platform (Shopify, WooCommerce, etc.) stored as a custom pick-list property on the HubSpot Company record.                                                                                      |
| `Order Reference.external_order_id`         | `Custom Shipment + Deal.external_order_id__c`  | merged                  | Order ID stored on both the Shipment custom object and the linked Deal, enabling cross-object lookups between CRM deals and shipment records.                                                                   |

## What to watch for in a SendCloud to HubSpot migration

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

high

### SendCloud has no native contact object — addresses are the contact proxy

SendCloud stores recipient and sender data as Address objects tied to shipments, not as standalone contact records.

How we handle it

There is no SendCloud contact with a persistent email record unless the address was used across multiple shipments. FlitStack deduplicates addresses by email during migration: when the same email appears across multiple SendCloud shipments, we create one HubSpot contact and associate all matching shipments to it. If an address appears only once and has no email, we create a contact with available fields and flag it for review. This behavior is specific to the SendCloud-to-HubSpot pair because most other CRMs have a contact object that SendCloud address data maps onto directly.

high

### HubSpot has no native shipment or logistics object — custom schema is required

HubSpot's standard CRM objects (Contact, Company, Deal, Ticket) have no fields for carrier name, shipping rate, tracking status, or return reason.

How we handle it

Migrating SendCloud data without creating HubSpot custom objects means losing the logistics layer entirely. FlitStack creates a Shipment custom object and a Return Request custom object in HubSpot before writing data, but this requires HubSpot Enterprise or Professional tier. We surface the exact custom-object schema required in the migration plan so your HubSpot admin can pre-approve the property creation in staging before the migration runs.

high

### SendCloud workflows have no HubSpot CRM equivalent and cannot migrate

SendCloud automations — carrier routing rules based on weight or destination, return-flow triggers, label-print conditions, and carrier-specific rate shopping logic — operate on logistics events that HubSpot workflows cannot observe.

How we handle it

HubSpot workflows trigger on CRM property changes, form submissions, deal stage updates, and similar CRM events, not on carrier scan events or shipment status changes. FlitStack documents every SendCloud automation as a rebuild reference specification and can map the trigger conditions to HubSpot workflow equivalents where the business logic overlaps (e.g., if a SendCloud return request should create a HubSpot ticket, we note that mapping). The automation rebuild itself is out of scope for the data migration.

medium

### SendCloud API rate limits constrain bulk export speed

SendCloud's API enforces rate limits that vary by account tier.

How we handle it

Large-volume migrations (500,000+ shipments) require pacing to stay within these limits, which extends migration clock time. FlitStack implements exponential backoff and respects SendCloud rate limit headers during extraction. We surface the estimated export duration based on your SendCloud plan tier during the discovery phase, and we can request a rate-limit increase on your behalf from SendCloud if your plan allows.

medium

### SendCloud tracking event history requires schema flattening for HubSpot storage

SendCloud stores tracking events as a chronological array per shipment (pickup scan, transit scan, delivery scan, return initiation, etc.) with individual timestamps and location data.

How we handle it

HubSpot has no native equivalent and no repeating or nested property structure for timeline events. We serialize the full event array into a single long-text property (Event\_Log\_\_c) on the Shipment custom object. This preserves all original timestamps and status codes but means the data is not queryable as individual HubSpot timeline entries — it is readable as a structured log. Teams that need per-event CRM automation triggers should rebuild those triggers using HubSpot workflow tools after migration.

## How the migration runs

1. ### Audit SendCloud data model and export API structure

   FlitStack connects to SendCloud via API using your account credentials and inventories all object types available: shipments, addresses, return requests, carriers, and any custom fields configured per shipment.

   What this step covers

   We map the SendCloud object graph — including how addresses link to shipments and how return requests link to original shipments — before writing any data. This audit produces a SendCloud-specific migration manifest that becomes the basis for the HubSpot schema plan.

2. ### Design HubSpot custom-object schema in staging

   Based on the SendCloud audit, FlitStack delivers a HubSpot schema plan: the custom Shipment object properties (carrier, service, status, rate, weight, label URL, event log), the custom Return Request object properties (status, reason, original shipment link), and the association labels to connect them to HubSpot Contacts.

   What this step covers

   Your HubSpot admin creates these in a staging portal before the migration run. We provide the exact property names, types, and pick-list values to minimize back-and-forth.

3. ### Match SendCloud users to HubSpot users by email

   SendCloud platform users are matched to HubSpot user accounts by email address.

   What this step covers

   Any SendCloud user with no matching HubSpot account is flagged in a pre-migration owner report. Your team resolves these before the migration run — either by inviting the user to HubSpot or by assigning their records to a designated fallback owner. No record migrates without a resolved owner.

4. ### Run sample migration with field-level diff

   A representative slice of SendCloud records — typically 200–500 shipments spanning multiple carriers, statuses, and return requests — migrates to HubSpot staging first.

   What this step covers

   FlitStack generates a field-level diff showing the exact values written to each HubSpot property. You verify carrier mapping, status value mapping, address-to-contact linkage, and owner resolution before the full run commits. The sample run also validates the delta‑pickup mechanism and confirms that owner assignment rules fire correctly across record batches. Adjustments to property types or pick‑list values can be made in staging before the production migration begins.

5. ### Execute full migration with delta-pickup window

   The full SendCloud dataset migrates to HubSpot.

   What this step covers

   A delta-pickup window of 24–48 hours after the main run captures any shipments created or updated in SendCloud during cutover. All operations are logged in an audit trail, and one-click rollback is available if the field-level diff reveals unexpected mapping behavior in the full run. FlitStack throttles API calls to respect SendCloud rate limits, preserving service stability. A record‑count checkpoint is taken after the run, and one‑click rollback removes only the migrated records if issues arise.

![](https://flitstack.ai/platforms/sendcloud.svg) SendCloud ![](https://flitstack.ai/platforms/hubspot.svg) HubSpot

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · HubSpot Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**72–96 hours for under 50,000 SendCloud shipment records** Typical, smaller accounts

**5–10 days for over 500,000 records or complex multi-object custom schema setups** Large or heavily customised accounts

A quote scales with the volume of SendCloud shipment and return-request records, the number of custom fields in use on those objects, and the complexity of the HubSpot custom-object schema required. A straightforward migration with one custom Shipment object, 10–20 custom fields, and under 25,000 records lands in the lower range. Configurations with multiple custom objects, N:N address associations, or tracking-event history spanning millions of rows push toward the upper range. HubSpot plan tier (Starter through Enterprise) does not directly affect migration cost but determines whether custom objects are available — Starter tiers cannot receive custom-object data without an upgrade. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for SendCloud to HubSpot →](https://flitstack.ai/contact)

## Why teams move from SendCloud to HubSpot

- SendCloud is a shipping platform with no CRM layer — as e-commerce operations grow, teams need HubSpot's contact-centric view to tie shipment history to customer records and deal context, not just logistics status. By mapping each SendCloud shipment to a HubSpot contact, sales, marketing, and service teams get a single view of every delivery event alongside deals, tickets, and lifecycle data. This removes manual look‑ups between a shipping portal and a CRM, reducing context‑switching and enabling timely outreach.
- SendCloud's reporting is carrier-performance focused. Customer voice from G2 and Capterra reviews indicates that teams outgrow SendCloud analytics when they need unified customer lifetime value reporting that spans pre-purchase, delivery, and post-purchase service — which HubSpot's CRM does natively. With HubSpot, the same data is available within the contact timeline, enabling managers to see order volume, delivery success rates, and post‑purchase support tickets in one dashboard without exporting spreadsheets.
- Companies consolidating their e-commerce and CRM into a single HubSpot instance (after using SendCloud for shipping alongside a separate CRM) want to eliminate the data silos between their logistics platform and their customer database. Moving shipment history into HubSpot custom objects closes that gap.
- SendCloud integration options for deeper customer segmentation are limited compared to HubSpot's CRM API. Teams that need shipping data driving lead scoring, deal intelligence, or service tickets find SendCloud alone insufficient at scale. HubSpot's API allows you to pull shipment status, carrier, and delivery timestamps directly into contact properties, triggering automated lead scoring updates, enriching deal records with delivery milestones, and creating support tickets when a shipment encounters a delay.

Questions, answered

## SendCloud to HubSpot migration questions

How long does a SendCloud to HubSpot migration take?

Most SendCloud-to-HubSpot migrations complete within 72–96 hours of clock time for under 50,000 shipment records. Larger datasets with 500,000+ records or complex multi-custom-object schemas extend to 5–10 days. The longest planning step is HubSpot custom-object schema design in staging before any data writes occur. During extraction, FlitStack reads shipment, address, and return‑request records via the SendCloud REST API, respecting rate‑limit headers. After the initial pass, a 24‑48‑hour delta window captures any new or changed shipments, ensuring HubSpot reflects the final SendCloud state at cut‑over. Validation checks compare record counts and property completeness before the migration is marked complete.

Will my SendCloud carrier routing rules and return-flow automations migrate to HubSpot workflows?

No. SendCloud automations — carrier routing based on weight or destination, return-trigger conditions, label-print logic — have no HubSpot CRM equivalent. HubSpot workflows operate on CRM events like property changes and form submissions, not on logistics events like carrier scans or shipment status changes. FlitStack documents every SendCloud automation as a rebuild reference specification so your HubSpot admin can rebuild equivalent logic in HubSpot workflow tools after migration.

What does a SendCloud recipient address become in HubSpot?

SendCloud stores recipient addresses as Address objects per shipment, not as persistent contact records. FlitStack deduplicates addresses by email: when the same recipient email appears across multiple shipments, we create one HubSpot contact with all address properties and associate every matching shipment to it. If an address has no email, we create a contact with available fields and flag it for manual review in HubSpot.

Can I migrate SendCloud return requests to HubSpot?

Yes. SendCloud ReturnRequest records migrate to a HubSpot custom object (Return\_Request\_\_c) with properties for return status, return reason, original SendCloud shipment ID, and return tracking number. The Return Request object is associated to both the HubSpot Contact and the original Shipment custom object. This requires a HubSpot Professional or Enterprise tier to support custom objects. FlitStack creates the Return\_Request\_\_c object in your HubSpot portal prior to migration, defines the required property types (pick‑list for status and reason, text for IDs), and associates it to the corresponding Shipment record via the original SendCloud shipment identifier. Teams using HubSpot Starter will need to upgrade before the migration writes these records.

What happens to SendCloud tracking event history in HubSpot?

SendCloud tracking events (carrier scans, delivery confirmations, return initiations) have no native HubSpot equivalent, so FlitStack serializes the full event history as a JSON-structured log in a custom long-text property (Event\_Log\_\_c) on the Shipment custom object. Original event timestamps and status codes are preserved. The log is readable but not queryable as individual HubSpot timeline entries — automation triggers on specific tracking events would need to be rebuilt in HubSpot workflow tools.

Does the migration affect my SendCloud account during the cutover?

No. FlitStack uses read-only API access on SendCloud — your team continues creating labels, processing returns, and managing shipments during the migration. A delta-pickup window of 24–48 hours after the main run captures any shipments created or updated in SendCloud during cutover so HubSpot reflects SendCloud's final state at go-live. Because FlitStack does not write to SendCloud, you can keep operating normally; the read‑only token only retrieves data, leaving your shipments, labels, and return requests untouched. The 24‑48 hour delta window then pulls any new or changed records after the initial extraction, ensuring HubSpot matches the live state when you switch over.

What HubSpot plan tier is required to receive SendCloud data?

HubSpot Starter tier cannot receive custom-object data — a Professional or Enterprise tier is required to create the Shipment and Return Request custom objects that store SendCloud carrier, tracking, and return data. FlitStack confirms your HubSpot tier during discovery and flags whether a plan upgrade is needed before the migration plan is finalized. Standard CRM objects (contacts, companies, deals) migrate to any HubSpot tier.

## Related migrations

[![](https://flitstack.ai/platforms-trim/hubspot.webp) Migrate to **HubSpot** Every source we move into HubSpot, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/hubspot)

### [HubSpot implementation](https://flitstack.ai/services/hubspot-implementation)

[Set up HubSpot and migrate into it as one engagement.](https://flitstack.ai/services/hubspot-implementation)

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**Vendasta to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/vendasta/to/hubspot) [**Capsule CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/capsule-crm/to/hubspot) [**Filevine to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/filevine/to/hubspot) [**Yardi to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/yardi/to/hubspot) [**Cision to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/cision/to/hubspot) [**Dynamics 365 to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/hubspot) [**SendCloud to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sendcloud/to/salesforce-sales-cloud) [**SendCloud to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sendcloud/to/zoho-crm)

## Sources: official documentation

1. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [Create and edit custom objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/object-settings/create-custom-objects)
3. [Import objects programmatically — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/import-objects)
4. [Understand property field types in HubSpot](https://knowledge.hubspot.com/properties/property-field-types-in-hubspot)
5. [Associate records on CRM objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/records/associate-records)
6. [Integration throughput and limits — HubSpot Knowledge Base](https://knowledge.hubspot.com/integrations/integration-throughput-and-limits)
7. [HubSpot Cloud Infrastructure and Data Hosting FAQ](https://knowledge.hubspot.com/account-security/hubspot-cloud-infrastructure-and-data-hosting-frequently-asked-questions)

Get a quote

## Moving from SendCloud to HubSpot?

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

[Get a quote](https://flitstack.ai/contact)
