Dynamically rename field headers to marketo field when importing lists | Community
Skip to main content
January 7, 2011
Delivered

Dynamically rename field headers to marketo field when importing lists

  • January 7, 2011
  • 27 replies
  • 6662 views
When I import a list, I currently have to rename each column header to be exactly the same as my marketo field name. It would be nice if I could simply choose the field I want associated with each header if it is not recognized  (similar to salesforce.com)

27 replies

March 28, 2012
It would be benificial if in the wizard you could map to the appropriate Marketo field via a dropdown.
February 24, 2012
So, yes, improvement is needed and field mapping would be wonderful.

I am just trying to find a list of the standard names of fields that are in marketo, so i can modify my csv file with the absolute correct header names.  Any clues where this exists?  Obviously, you cannot go by what is in the UI, as we all know that Email is not Email or email or email address but exactly Email Address.  Crazy.
January 12, 2012
I'm having a TOUGH TIME importing my data into Marketo. No doubt this is necessary.
December 8, 2011
+1 this is a pain
October 7, 2011
I agree with this as well.  As a former Eloqua user I find it really frustrating that you don't have the ability to map fields.  Please work on implementing this feature.  It's a small thing that would make a HUGE difference.
August 10, 2011

Hard to believe this hasn't been implemented since 1/11...

August 10, 2011

Hard to believe this hasn't been implemented since 1/11...

June 23, 2011
Would be very useful, as I have wasted a lot of valuable time trying to get the headings mapped correctly!!
Edward_Masson
New Participant
May 19, 2011
(Subscribing to thread)
May 18, 2011
This would make the list import process so much easier! I previously used Vertical Response and they automatically mapped the fields from the Excel spreadsheet to their fields and gave you the ability to choose the correct field if the field they automatically chose was incorrect. And I agree that case sensitive field names and and extra space errors are a pain!