Lime CRM to HubSpot
Lime CRM is a relational CRM on Microsoft SQL Server. Each customer's data model is customised.
Lime CRM data can move into HubSpot, landing mainly in Sales Hub. 3 of 7 mapped objects move directly (Companies, Persons and Deals); 4 items need manual work and 3 do not move. Plan roughly 3-6 weeks for a small move and 12-24 weeks for a large one.
Migration checklist for Lime CRM
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
<50k records
CSV-based, basic objects.
Mid migration
50k-500k records
API extraction, activities and files.
Large migration
>500k records
Custom limetypes, heavy rebuild.
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 Lime CRM: what you need to get in, what lands in HubSpot, and what will not.
REST (Limetype, Limeobject, File and Query APIs) over HTTPS, with per-application interactive docs
API key for a dedicated API user, plus the tenant base URL (https://<domain>/<application>/api/v1).
Admin access to the Lime CRM Server Administration interface (LISA) to create the API user and key. Group policies apply to the API user's reads.
Choose your route
How will you move the data?
No native connector was found.
- You need: API key for a dedicated API user, plus the tenant base URL (https://<domain>/<application>/api/v1).
- Permission: Admin access to the Lime CRM Server Administration interface (LISA) to create the API user and key. Group policies apply to the API user's reads.
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.
- Self-service CSV/Excel export, limited to admins or users with export permission
- REST API returning JSON
- Full SQL Server backup (.bak) on request via support
- Assisted migration by Lime Expert Services
Limits: To confirm
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: 12-24 weeks, usually phased.
Talk to a partnerWhere each object lands
In Lime CRM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Companies | Companies | yes | Each entity type exports as a separate dataset with identifiers that preserve relationships. |
| Persons | Contacts | yes | Lime's standard 'person' type maps to Contacts. Custom fields vary by application. |
| Deals | Deals | yes | Pipeline and stage values must be mapped to HubSpot pipelines. |
| Activities (history, notes, todos) | Notes, Calls, Meetings, Tasks | partial | The type names and structure depend on the custom data model. Confirm export coverage per table. |
| Documents/files | Files | partial | The File API gives access to binary data. Association to records must be rebuilt. |
| Users/owners | Contacts | manual | Map Lime users to HubSpot users and owners by email. |
| Custom limetypes | Custom objects | partial | Discover them via the Limetype API. |
What to expect
These are platform code and configuration, not data.
Lime policies do not map to HubSpot permission sets.
They are not exportable as definitions.
Source logic is in custom adaptations.
Lime policies are applied per user and group.
They are not portable.
CSV exports are per table, so associations must be re-joined by ID.
Keep Lime IDs as a HubSpot custom property and import associations in a separate pass.
Confirm with the Lime account manager, or use the SQL backup or assisted export.
Use the tenant's /api/v1/docs/ and Limetype metadata to inventory fields.
Store the key in a vault and revoke it after cutover.
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.
Export paths and API auth are backed by Lime docs. Object-to-HubSpot mapping, rate limits, and the native connector status rest on category-level knowledge, because Lime's data model is customised per application.
Sources
Related migrations
Frequently asked questions
How do I migrate Lime CRM to HubSpot?
1. Inventory limetypes and fields via the Limetype API and /api/v1/docs/. 2. Create a dedicated API user in LISA, add it to a group with read policies, and generate the API key. 3. Confirm with Lime whether REST API use needs an extra license, or request the .bak export. 4. Decide which Lime fields map to HubSpot properties, and create the custom properties, including a Lime ID.
What data can move from Lime CRM to HubSpot?
These objects move directly: Companies, Persons and Deals. Check the mapping table for partial and manual items.
What does not move from Lime CRM to HubSpot?
Automation, VBA and Python application adaptations, and webhooks, Permission policies and groups and Lime dashboards and reports. Plan to rebuild or retire these.
How long does a Lime CRM to HubSpot migration take?
Small (<50k records): 3-6 weeks. Mid (50k-500k records): 6-12 weeks. Large (>500k records): 12-24 weeks. These are planning estimates, not a quote.
What access do I need to export from Lime CRM?
API key for a dedicated API user, plus the tenant base URL (https://<domain>/<application>/api/v1). Admin access to the Lime CRM Server Administration interface (LISA) to create the API user and key. Group policies apply to the API user's reads.
What compliance issues apply when moving Lime CRM data?
Check: Check for sensitive data in notes and files. Agree consent, retention and access rules before exporting.
Moving Lime 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