Migrate from Lucep to HubSpot

Lucep's lead record maps directly to HubSpot contact. The primary email, phone, name, and company association transfer as HubSpot standard properties. Qualification status from Lucep maps to HubSpot lifecycle_stage using a value-mapping table where each Lucep status maps to the closest HubSpot lifecycle stage.

Lucep company records map 1:1 to HubSpot companies. Company name, domain, industry, employee count, and annual revenue transfer to HubSpot's matching standard properties. If Lucep stores a parent/child hierarchy, the top-level company migrates first, then child companies link via the Parent Company field.

Lucep deal records map to HubSpot deals with deal name, amount, owner, close date, and status transferred. If Lucep stores a single deal stage, it maps to the first stage in your HubSpot deal pipeline. Multi-stage Lucep setups use the pipeline field to determine which HubSpot pipeline each deal belongs to.

Lucep's callback records — AI voice agent calls, manual outbound callbacks, and retry attempt logs — migrate as HubSpot call engagements. Each engagement records the original call timestamp, duration, outcome (answered, missed, voicemail), and owner link. The disposition code from Lucep stores as a custom property on the engagement for reporting parity.

Lucep's numeric lead score has no native HubSpot equivalent in free or Starter tiers. We create a custom numeric property called Lead_Score_Lucep__c on the HubSpot contact object and populate it from Lucep's lead_score field. Your team can use this as-is or replace it with HubSpot's native scoring when you enable Operations Hub.

Lucep's routing rules — round-robin distribution, weighted assignment, and skill-based routing — cannot map to a HubSpot native object because HubSpot has no built-in routing engine. We export the full rule definitions (criteria, weights, fallback logic) as a structured JSON document. Your HubSpot admin uses this as a blueprint to rebuild routing using HubSpot Workflows or Operations Hub business rules.

Lucep's qualification status field (e.g., New, Contacted, Qualified, Unqualified) maps to HubSpot's lifecycle_stage pick-list via a value-mapping table. 'Qualified' in Lucep maps to 'MQL' or 'SQL' in HubSpot depending on your definition. Unmapped Lucep statuses default to 'lead' lifecycle stage with a flag property preserving the original Lucep value.

Lucep user records resolve to HubSpot owners by email matching. If a Lucep owner email matches an existing HubSpot user, the HubSpot owner record links automatically. Unmatched owners are flagged in a pre-migration report — your team either creates HubSpot users for them before migration or assigns their records to a fallback owner.

Lucep file attachments associated with leads, companies, or deals re-upload to HubSpot Files linked to the corresponding contact, company, or deal record. File size limits per HubSpot's 25MB per-file constraint apply. Files are rehosted in HubSpot's file storage with the original filename preserved.

Lucep's logged email activities migrate as HubSpot email engagements with original sent timestamp, subject, body content, and owner link preserved. Email content transfers as plain text or HTML depending on what Lucep stored. Attachments to emails follow the HubSpot file attachment workflow.

Any Lucep custom fields beyond the standard set map to HubSpot custom properties. We create the custom property in HubSpot with the matching field type (text, number, date, picklist, etc.) and populate it during migration. Field-level validation rules in HubSpot can be applied post-migration if needed.

Lucep stores call recording URLs as metadata on callback records. Because HubSpot engagements don't natively host call recordings, we migrate the recording URL as a custom text property on the HubSpot contact or deal so your team can access the recording by clicking the link. Note: the recording file must remain accessible on Lucep's storage or be downloaded separately.