Export/Import of Leads (through the Prospecting feature)

[JBroadley4]

The introduction of Prospecting to manage leads is a welcome addition to HubSpot.  We have adopted it and over all it works really well.

However, some of the standard functionality in how you manage other record types (companies, deals and contacts) aren't available for Lead records.  This includes: exporting leads to a spreadhseet, and the ability to make wholesale changes to that export and re-import it back into HubSpot.  The ease of use of HubSpot doesn't seem to apply to Lead records which is frustracting and hard to understand.  Can this be fixed to make data management of lead data easier and encourage the adoption of the Lead feature in HubSpot?  

[RBozeman]

Yes, this would be a great feature to have. Leads, in general, should receive all of the features that are available for all major record types. I suspect it will over time. 

[aericks2]

Totally agree.  I need migrate "leads" from another CRM for a client and this is currently not possible.   It sounds like there is no import wizard like there is for contacts / companies / deals.  But not sure if this is true for API as well. 

A work around might be using a lifecycle stage to generate new leads through the interface, but that is only a partial solution and not ideal for a company migrating in to HubSpot with active Leads in flight.  

[JLipson]

The lifecycle stage to "pull leads in" is not a complete solution for companies that view a contact as being able to be a lead multiple times in their lifecycle with a company. (Cross-sell)

when we are importing contacts we need the ability to trigger some contacts of those as leads too and to be able to upload against the associated properties in the lead workspace. 

[ECals]

I agree, it's really surprising to see that the lead object have less fonctionalities that other object in HubSpot, however a simple custom object have more fonctionnality and option than this one in my opinion... Can't wait to see the previous updates, cause I'm sure something is on the backlog on HubSpot side!