Migrate from Lime Go to HubSpot

Lime Go contacts map 1:1 to HubSpot contacts. The Lime Go firstname, lastname, email, phone, jobtitle, and address properties become HubSpot's corresponding contact properties. Owner assignment resolves by email match against HubSpot users — unmatched owners surface as a pre-migration flag.

Lime Go company records map to HubSpot companies. Lime Go's built-in Nordic company database enriches company name, domain, and industry — these map to HubSpot's company name, domain, and industry pick-list. Parent-child company hierarchies in Lime Go map to HubSpot's parent company association.

Lime Go deals map to HubSpot deals. Deal name, amount, close date, owner, and stage from Lime Go become HubSpot deal properties. Lime Go's stage names map value-by-value to HubSpot deal-pipeline stages — we generate the stage map from your Lime Go pipeline configuration before migration runs.

Each Lime Go deal stage maps to a named HubSpot deal-pipeline stage. Probability and forecast-category values apply from HubSpot's stage settings based on the target pipeline. Lime Go stage-entry timestamps are not a native HubSpot field — we preserve them as a custom datetime property on the deal.

Lime Go activity history (calls, emails, meetings, notes per contact or deal) migrates as HubSpot engagements. Call logs become HubSpot calls with original timestamps and owner attribution. Email activity becomes HubSpot email engagements. Meeting records become HubSpot meeting engagements with start and end times preserved.

Lime Go custom fields map to HubSpot custom properties. The migration reads Lime Go's custom field definitions, creates matching properties in HubSpot (with the correct type — text, number, date, pick-list, checkbox), then populates them during the data load. Lime Go tag data that uses a multi-select pattern converts to a HubSpot multi-checkbox or text property depending on volume.

Lime Go documents and files attached to contacts, companies, or deals re-upload to HubSpot Files. Inline files in Lime Go notes download and rehost in HubSpot's file storage. File size limits on the HubSpot side are checked — files exceeding 25MB split or flag for manual handling.

Lime Go owner records resolve by email match against HubSpot users. A pre-migration audit reports any Lime Go owner without a corresponding HubSpot user — your team decides whether to invite them to HubSpot first or assign their records to a fallback owner. No record lands without a valid HubSpot OwnerId.

Lime Go tags used for segmentation map to HubSpot custom properties (single or multi-select depending on tag volume) or HubSpot lists. High-frequency tags (more than 50 distinct values) convert to a multi-select property; lower-frequency tags become a single-select. We surface the tag distribution before migration so you choose the approach.

Lime Go history notes per record migrate to HubSpot's timeline as engagement notes with the original author and timestamp. Rich-text formatting in Lime Go notes is preserved where HubSpot's note format supports it. Notes attached to specific deals also link to the corresponding HubSpot deal timeline.

Lime Go users map to HubSpot users by email. Lime Go team structures map to HubSpot teams for reporting-scope alignment. If your Lime Go setup uses role-based access, we map it to HubSpot's permission sets — sharing rules and page layout assignments are destination-side configuration your HubSpot admin sets after migration.

Lime Go's GDPR functionality (consent tracking, anonymisation history) does not have a native HubSpot equivalent. We map consent records as HubSpot subscription-type custom properties with a source_consent_timestamp datetime field. Your HubSpot admin configures HubSpot's subscription types to match your consent categories post-migration.