We will need to be doing a daily import from a CVS for a new process going forward. Does anyone know of a way that a prior mapping for import can be saved so that we don't have to remap every time?
Mai 18, 20189:15 AM - bearbeitet Mai 18, 20189:15 AM
Vordenker/-in
reusable mapping template for import
lösung
Does my post help answer your question?
Help the Community by marking it as SOLVED
Q: Reusable mapping template for import?
Short A: No. No need.
Longer A:
We do lots of large (>50K) imports for clients across multiple portals and here's a couple things we've learned to make life MUCH EASIER.
-1- Use the correct HubSpot property names in your .csv.
This totally eliminates the need for what you refer to as a 'mapping template'.
-2- Unless you're just importing a handful of records, always, always, always test your .csv with a single record or two before performing the full import.
Can't even begin to tell how much time this will save you from having to read those horrible error files. haha
-3- Consider setting up a 'Staging CRM'.
Staging your imports in an intemediary CRM does make the process a bit more comlex, but complexity is a relative term. Large &/or repeated imports are perfect opportunities to totally ruin the integrity of CRM data.
We can either practice prevention, or run around like chickens with our heads cut off trying to put out fires. Guess you have to ask yourself if you'd rather be a smoke-detector (and priactice fire prevention) or a fireman.
For anyone viewing this thread on the community, I wanted to ensure you saw that we have just launched the ability to repeat a past import. When repeating an import, you will not only be able to skip specific steps within the import flow, but we'll also save the selections you've made on the mapping step so you can move more quickly through the import flow.
For anyone viewing this thread on the community, I wanted to ensure you saw that we have just launched the ability to repeat a past import. When repeating an import, you will not only be able to skip specific steps within the import flow, but we'll also save the selections you've made on the mapping step so you can move more quickly through the import flow.
Reuseable Template definitions for imports are a must have. I am horrible missing them in hubspot.
The reason is, that properties have the same names in contacts and company records. So defining a header row in excel is not sufficient to get a unique match.
We have to import files from our external sales agents on daily basis and i have always to make the correction of the object in hubspot (from contacts to company).
Please provide such a functionality to make life easier for users with a lot of imports.
I will highly encourage you to create the idea in our idea's forum.
The product team is in charge of checking these ideas, they will review the possibility to added it and implemented in the future. The more people upvote and need the idea, more chances 🙂
Mai 18, 20189:15 AM - bearbeitet Mai 18, 20189:15 AM
Vordenker/-in
reusable mapping template for import
lösung
Does my post help answer your question?
Help the Community by marking it as SOLVED
Q: Reusable mapping template for import?
Short A: No. No need.
Longer A:
We do lots of large (>50K) imports for clients across multiple portals and here's a couple things we've learned to make life MUCH EASIER.
-1- Use the correct HubSpot property names in your .csv.
This totally eliminates the need for what you refer to as a 'mapping template'.
-2- Unless you're just importing a handful of records, always, always, always test your .csv with a single record or two before performing the full import.
Can't even begin to tell how much time this will save you from having to read those horrible error files. haha
-3- Consider setting up a 'Staging CRM'.
Staging your imports in an intemediary CRM does make the process a bit more comlex, but complexity is a relative term. Large &/or repeated imports are perfect opportunities to totally ruin the integrity of CRM data.
We can either practice prevention, or run around like chickens with our heads cut off trying to put out fires. Guess you have to ask yourself if you'd rather be a smoke-detector (and priactice fire prevention) or a fireman.