Migrate from LeadManaging to HubSpot

Every LeadManaging lead record maps to a HubSpot contact. Standard properties (name, email, phone, address) map directly to HubSpot's built-in contact properties. The original LeadManaging record ID is preserved in a custom property for traceability and delta-run de-duplication. This custom property is named source_record_id__c and remains read‑only in HubSpot, ensuring that any future sync can reference the original source identifier without manual lookup.

LeadManaging lead statuses (e.g. New, Qualified, Converted, Lost) map to HubSpot lifecycle stage values if an equivalent exists. Custom statuses without a HubSpot equivalent become a HubSpot custom pick-list property (LeadManaging_Status__c) so historical reporting is preserved without altering HubSpot's operational lifecycle stage field.

HubSpot has a built-in Source field for contacts. If LeadManaging stores the lead source in a named property, FlitStack maps it to HubSpot's native hs_analytics_source_data_1. If the property name is ambiguous, a custom property is created and the original field name is preserved in the mapping plan.

LeadManaging owner IDs resolve to HubSpot owners by email match. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts for them or assigns records to a fallback owner. No contact lands without a HubSpot owner.

LeadManaging has no standalone company object — company names embedded in lead records are extracted, deduplicated, and inserted as HubSpot company records before contacts are associated. Contacts without an identifiable company become unassociated or attach to a placeholder company record.

If LeadManaging stores deal value or pipeline stage, FlitStack creates HubSpot deal records linked to the migrated contact and company. Pipeline stage values map to HubSpot deal stage values per pipeline. Probability and forecast category are applied based on HubSpot's stage configuration.

Call records with timestamp, duration, outcome, and owner map to HubSpot call engagements linked to the contact record. Original call date and owner are preserved. HubSpot's call recording attachment migrates as a file on the engagement. If the call includes notes or a disposition code, those are stored in custom properties on the engagement record. The duration field is recorded in seconds for consistent reporting.

Email records (sent, opened, clicked) migrate as HubSpot email engagements with original timestamps. The email subject, body content, and association to the contact are preserved. HubSpot's email template association is not carried over since templates do not migrate. If the original email includes attachments, they are migrated as files linked to the engagement, maintaining the full communication context for audit and follow-up.

Meeting records with title, start time, end time, location, and attendees map to HubSpot meeting engagements. The linked contact and company are preserved. HubSpot meeting links or video conference URLs stored in LeadManaging are carried as text properties. If the meeting includes a description or notes, those are migrated as custom properties on the engagement to preserve any relevant context for future reference.

Notes attached to a LeadManaging lead record migrate as HubSpot notes linked to the corresponding contact. Rich-text formatting is preserved as plain text. Note create dates and owner associations are retained for audit continuity. If a note includes any attachments, those files are migrated as linked files to the note, ensuring that all supporting material is available in HubSpot for future review.

Any LeadManaging custom fields not matching HubSpot's built-in property names become HubSpot custom properties on the contact object. Property type (text, number, date, currency, pick-list) is inferred from the source data format. Starter plan users should review property count limits before migration.

LeadManaging workflows and automation rules do not migrate. FlitStack AI exports workflow definitions as a structured JSON reference document for your HubSpot admin to rebuild in HubSpot's workflow builder. Rule logic, triggers, and conditions are preserved as documentation. The exported file includes the original rule name, each step's action type, and any field-change conditions, giving your admin a step-by-step blueprint to recreate the automation in HubSpot.

LeadManaging reporting configurations and dashboards do not migrate. Underlying data (contact counts, deal values, activity history) is available in HubSpot after migration, but report definitions must be rebuilt using HubSpot's analytics tools. We provide a data inventory so your admin knows which metrics are available.