Raynet CRM to HubSpot
Cloud CRM (Czech-origin) with accounts, contacts, leads, deals (business cases), activities, products, offers, orders and invoices.
Raynet CRM data can move into HubSpot, landing mainly in Sales Hub. 4 of 8 mapped objects move directly (Accounts (companies), Contacts (persons), Deals (businessCase) and Products); 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 Raynet CRM
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 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
XLSX-based.
Mid migration
10k-100k
API extraction.
Large migration
>100k
Includes activities, files and documents.
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 Raynet CRM: what you need to get in, what lands in HubSpot, and what will not.
REST (v2, JSON, OpenAPI/Swagger)
Instance name, username and API key from Application settings > For developers > API keys.
Admin user to create API keys and to run XLSX imports; SQL backup is requested through Raynet support.
Responses carry X-Ratelimit headers; the sample shows a limit of 24000 per instance. The exact window is not confirmed.
Choose your route
How will you move the data?
No native connector was found.
- You need: Instance name, username and API key from Application settings > For developers > API keys.
- Permission: Admin user to create API keys and to run XLSX imports; SQL backup is requested through Raynet support.
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.
- XLSX export from each list view (200 records per export when selecting rows; up to 7500 via the three-dots menu 'All columns')
- Datový rejstřík states the default export cap is 10,000 rows, which conflicts with the help-centre 7500 figure
- REST API export, including activities
- SQL backup of the full instance on request via support
Limits: Responses carry X-Ratelimit headers; the sample shows a limit of 24000 per instance. The exact window is not confirmed.
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 Raynet CRM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Accounts (companies) | Companies | yes | Available through API /company/ and XLSX export. |
| Contacts (persons) | Contacts | yes | API /person/ and XLSX export; custom fields are exported only if flagged exportable. |
| Leads | Contacts | partial | Leads have no direct HubSpot equivalent; map to Contacts or Companies with lead status, or to Deals. This is a design decision. |
| Deals (businessCase) | Deals | yes | API /businessCase/ includes phase changes; the XLSX template covers only accounts, leads and products. |
| Activities (tasks, meetings, calls, emails, letters) | Tasks | partial | Exportable via API and XLSX list. Maps to Tasks, Meetings, Calls, Emails or Notes; the association export needs testing. |
| Products | Products | yes | XLSX export, and the template allows import and update. |
| Offers, orders, invoices | Quotes | manual | Present in the API (offer, salesOrder, invoice). Invoices have no native HubSpot object; use Custom objects or archive the PDFs. |
| Users/owners | Contacts | manual | Re-map owners by email to HubSpot users; the Raynet export route for users was not verified. |
What to expect
No migration path was found in the sources; rebuild them in HubSpot Workflows.
Not exportable as found; recreate them in HubSpot teams and permission sets.
Rebuild them in HubSpot reporting.
HubSpot pipelines and stages must be created before the deal import.
Raynet has a separate Lead record type that HubSpot lacks.
The API has DMS document endpoints, but HubSpot Files uploads need scripting.
List exports may not carry link IDs; verify them via the API.
Export via the API and keep the Raynet IDs as HubSpot properties.
Use the API with paging, or request an SQL backup.
Confirm the plan or upgrade temporarily before extracting.
Enable the flag on every custom field before exporting.
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.
Access, export and API are backed by Raynet docs and help-centre pages. Object-to-HubSpot mapping, the HubSpot-side connector check, governance and pipelines/permissions/automation export rest on category-level knowledge and were not verified against HubSpot docs.
Sources
Related migrations
Frequently asked questions
How do I migrate Raynet CRM to HubSpot?
1. Confirm the Raynet plan includes API access. 2. Create an admin API key and note the instance name. 3. Flag all custom fields as exportable. 4. Take an XLSX and SQL backup via support.
What data can move from Raynet CRM to HubSpot?
These objects move directly: Accounts (companies), Contacts (persons), Deals (businessCase) and Products. Check the mapping table for partial and manual items.
What does not move from Raynet CRM to HubSpot?
Automation/workflow rules, Permissions and roles and Reports and dashboards. Plan to rebuild or retire these.
How long does a Raynet CRM to HubSpot migration take?
Small (<10k): 2-4 weeks. Mid (10k-100k): 4-8 weeks. Large (>100k): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Raynet CRM?
Instance name, username and API key from Application settings > For developers > API keys. Admin user to create API keys and to run XLSX imports; SQL backup is requested through Raynet support.
What compliance issues apply when moving Raynet CRM data?
Check: EU GDPR applies to the Czech-origin vendor and EU customers and Invoices are financial records. Agree consent, retention and access rules before exporting.
Moving Raynet CRM 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