Import issue

Data Hub Data Hub
1

Hi,

I have a problem. I’m trying to upload the Lifecycle Stage field for 16k records. It says it was successful and received. Unfortunately, it wasn’t, and most of it wasn’t updated. The format is fine. Can someone help me?

2

Hi @KSyguła,

Have you checked whether there were any import errors? Review and troubleshoot record import errors

@KSyguła wrote:

It says it was successful and received. Unfortunately, it wasn’t, and most of it wasn’t updated.

Could you please be a bit more specific?

  • Were empty fields not filled?
  • Were existing values not overwritten to your expectations?

Keep in mind that lifecycle stage values will never be set back by an import, they will only go forward. Also keep in mind that there might have been import errors and unless you resolved them, HubSpot would for example not have imported a “MQL” when your lifecycle stage is “Marketing Qualified Lead”.

Best regards

3

Hi @KSyguła I can see why this would be frustrating. If HubSpot shows the import as successful but data isn’t updated, it’s often tied to one of a few issues, so here’s a breakdown to troubleshoot:

  1. Import Errors: Make sure to check the import logs or the “Import History” tab for any errors, as Karsten mentioned. Sometimes the import success message appears, but there are warnings or errors related to certain records.
  2. Field Format: Ensure that the values you’re importing for the Lifecycle Stage field match exactly what HubSpot expects. Lifecycle stages like “Marketing Qualified Lead” (MQL) need to be case-sensitive, so make sure there are no discrepancies.
  3. Lifecycle Stage Direction: HubSpot’s lifecycle stage is a forward-moving field, so if you’re trying to import records with an outdated lifecycle stage (e.g., setting “Marketing Qualified Lead” to a lower stage like “Lead”), it won’t update because HubSpot only allows progression.
  4. Mapping Issues: Check your field mappings. If any required fields are missing or mismatched, the records may not update as expected. Sometimes an overlooked field causes part of the import to fail.
  5. Data Syncing Consideration: If you’re syncing this data with other platforms using Stacksync or a similar tool, ensure the syncing process doesn’t interfere with HubSpot’s import logic. You may need to perform a sync operation to push the data after it’s imported, ensuring consistency across systems.

Let me know if any of these suggestions help or if you find any specific errors in your logs.