Migrate from Lemon Tech to HubSpot

Lemon Tech person records map directly to HubSpot contacts. The primary company association in Lemon Tech becomes the HubSpot contact's primary company association. Multiple company associations require HubSpot's association model — the primary company is mapped first, secondary associations are created as additional company links.

Lemon Tech company records map 1:1 to HubSpot companies. Company hierarchies (parent/child relationships) in Lemon Tech preserve as HubSpot parent company associations. Domain-based company matching in HubSpot is enabled post-migration for automatic duplicate detection on new imports. Additional fields such as industry classification, employee count, and address details migrate directly, and any custom properties on the company object are created in HubSpot before import to ensure schema consistency.

Lemon Tech deal records map to HubSpot deals with deal name, amount, close date, and stage migrated. Each Lemon Tech pipeline maps to a HubSpot deal pipeline. Stage values map to HubSpot deal stages by name with probability weights re-applied from HubSpot's stage configuration.

Lemon Tech pipelines become HubSpot deal pipelines. HubSpot allows multiple pipelines per portal, and each pipeline has its own set of stages with custom probability and forecast settings. Pipeline-level settings from Lemon Tech (if configurable) migrate as pipeline metadata attached to the HubSpot pipeline configuration.

Lemon Tech engagement records (calls, emails, meetings) map to HubSpot engagement records attached to parent contact. Timestamps, owners, and body content are preserved. HubSpot's engagement timeline displays these activities chronologically on each contact record. Each activity type uses its corresponding HubSpot engagement type, and attachments are referenced by URL after re‑uploading to HubSpot Files. For large volumes, FlitStack uses HubSpot's bulk import to respect API rate limits while maintaining fidelity.

Lemon Tech notes migrate as HubSpot engagement notes attached to parent contact or company. Rich-text formatting in Lemon Tech notes is preserved as HTML within HubSpot's note body. Timestamp and owner attribution migrate for audit continuity. If notes contain inline images, FlitStack extracts the files, re-uploads them to HubSpot Files, and updates image URLs in the HTML to point to the new locations, preserving visual integrity.

Lemon Tech owner records are resolved by email match against HubSpot user accounts. FlitStack AI performs an email lookup against HubSpot's user directory before migration. Records with unmatched owner emails are flagged and assigned to a designated fallback owner specified by the customer.

Lemon Tech custom fields on any object become HubSpot custom properties on the equivalent object. FlitStack AI creates the custom property in HubSpot with the appropriate field type (string, number, date, checkbox, picklist) before migrating data. Picklist fields require value-by-value mapping if Lemon Tech uses custom picklist values.

Lemon Tech custom entities map to HubSpot custom objects (available on HubSpot Professional and Enterprise tiers). Custom entity associations that use N:N relationships in Lemon Tech require HubSpot custom relationship definitions. FlitStack maps the association schema and validates relationship integrity post-migration.

Lemon Tech file attachments on records re-upload to HubSpot Files and are linked back to the parent record. File size limits apply per HubSpot's file storage configuration (25MB per file). Inline images in notes are extracted, rehosted, and the reference URLs are updated in the note body.

If Lemon Tech tracks a lifecycle or status property on contacts, that value maps to HubSpot's lifecycle_stage property by value. Lemon Tech records without a lifecycle value default to 'lead' in HubSpot. Customers can override this default mapping during the planning phase.

Lemon Tech lead status values map to HubSpot's hs_lead_status property. Custom status labels in Lemon Tech require explicit value-by-value mapping against HubSpot's lead status pick-list options. Status history (timestamps) is preserved as a custom datetime property for reporting continuity. During migration, FlitStack validates that each mapped status value exists in HubSpot's pick-list; any missing values are flagged for customer review before the import runs to avoid data rejection.