Sellsy to HubSpot
French SaaS CRM, invoicing and sales management suite for B2B and B2C. Companies and individuals carry a prospect, client or supplier status.
Sellsy data can move into HubSpot, landing mainly in Sales Hub. 2 of 7 mapped objects move directly (Companies (prospect/client/supplier) and Contacts / individuals); 4 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Sellsy
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<10k contacts/companies, 1 pipeline
CSV-based migration.
Mid migration
10k-100k records, several pipelines, comments and tasks
API-assisted extraction plus automation rebuild.
Large migration
>100k records, heavy history and documents, multi-team
Custom scripting and phased cutover.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Sellsy: what you need to get in, what lands in HubSpot, and what will not.
REST API v2 (OAuth 2.0), plus legacy API v1 callable via v2 credentials
Client ID and Client Secret created in Menu > Settings > Developer portal, with scopes selected.
Token privileges follow the creator's, so an administrator should create the API access. Exports need export rights in the privilege profile.
Daily quota depends on the plan. A third-party source reading Sellsy's October 2026 pricing page gives 50,000 to 432,000 requests/day.
Choose your route
How will you move the data?
No native connector was found.
- You need: Client ID and Client Secret created in Menu > Settings > Developer portal, with scopes selected.
- Permission: Token privileges follow the creator's, so an administrator should create the API access. Exports need export rights in the privilege profile.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- CSV export from any list via Actions (displayed or all columns)
- Advanced export to JSON/PARQUET and PDF
- Export of linked comments, delivered as a zip with the entity CSV
- Export history under Settings > Data > Data export
- Sales document line export
- Accounting journal export (FEC/CSV)
- API v2 pagination for full extraction
Limits: Daily quota depends on the plan. A third-party source reading Sellsy's October 2026 pricing page gives 50,000 to 432,000 requests/day.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Sellsy
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Companies (prospect/client/supplier) | Companies | yes | Status (prospect/client/supplier) has no direct HubSpot equivalent. Map it to lifecycle stage or a custom property. |
| Contacts / individuals | Contacts | yes | Contacts may or may not be linked to a company, so the company association has to be rebuilt from export IDs. |
| Opportunities | Deals | partial | The Make docs list opportunities as an API object. Pipeline and stage mapping and the export columns need checking. |
| Comments on records | Notes | partial | CSV export of linked comments is available for clients, prospects, suppliers, contacts and opportunities. Notes must be loaded through import or API. |
| Tasks and events | Tasks | partial | The Make docs list events and tasks as API objects. Calls, emails and meetings would need mapping and are not confirmed. |
| Catalog products and document lines (quotes, orders, invoices) | Products | partial | Line export is available in CSV, JSON and PARQUET. Quotes and Line items need API or custom-object work. |
| Collaborators (owners) | Contacts | manual | Match owner names or emails to HubSpot users before import. |
What to expect
No export path found in the sources reviewed. Rebuild them in HubSpot.
Rebuild them as HubSpot roles and permission sets.
Rebuild them in HubSpot. Sellsy exports provide raw data only.
Needed before import so values map correctly.
The sources do not confirm which activities and links the exports and API include.
Sellsy stores files on contacts, clients, opportunities and products. Bulk export of them is not confirmed.
HubSpot is not an invoicing system, so keep them in an accounting tool or archive them.
Store the Sellsy ID in a custom property on each HubSpot object.
Link the API access to a stable administrator account for the whole project.
Run extraction in batches or use advanced JSON/PARQUET exports.
Run a separate comments export and merge it by record ID.
Enable the API V1 scope and use OAuth bearer tokens against the v1 endpoint.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
API auth and export paths are backed by Sellsy docs. Object-to-HubSpot mapping, activity/association export coverage, governance and any HubSpot-side connector rest on category-level knowledge. I found no HubSpot docs for Sellsy.
Sources
Related migrations
Frequently asked questions
How do I migrate Sellsy to HubSpot?
1. Create an admin-owned API access in the Developer portal with all needed scopes. 2. Inventory custom fields, pipelines, privilege profiles and automations. 3. Confirm your plan's daily API quota. 4. Test whether each list export includes IDs and the company links.
What data can move from Sellsy to HubSpot?
These objects move directly: Companies (prospect/client/supplier) and Contacts / individuals. Check the mapping table for partial and manual items.
What does not move from Sellsy to HubSpot?
Automations/workflows, Privilege profiles and permissions and Reports and dashboards. Plan to rebuild or retire these.
How long does a Sellsy to HubSpot migration take?
Small (<10k contacts/companies, 1 pipeline): 2-4 weeks. Mid (10k-100k records, several pipelines, comments and tasks): 4-8 weeks. Large (>100k records, heavy history and documents, multi-team): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Sellsy?
Client ID and Client Secret created in Menu > Settings > Developer portal, with scopes selected. Token privileges follow the creator's, so an administrator should create the API access. Exports need export rights in the privilege profile.
What compliance issues apply when moving Sellsy data?
Check: Financial/invoicing data and Possible B2C personal data (GDPR). Agree consent, retention and access rules before exporting.
Moving Sellsy into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner