RELATED IDEAS
Improve user experience of CSV import
What is the challenge?
Properly configuring a csv file for import is challenging and confusing
When importing the logs don't provide useful information especially when a record was successfully created but some fields didn't populate correctly
It's difficult to determine how to configure the csv file for import (what kind of separator to use when there are multiple entries for a field, how to refer to other Aha records in custom fields, etc)
What is the impact?
Using the CSV import is frustrating
Wasted time trying to get the import to work properly
Limits use of Aha when lists created elsewhere cannot be imported
Describe your idea.
Clearer documentation about how to configure the csv to import properly, either in the "what fields can I import" page or listed in the Aha KB
-
Specific things:
How to separate multiple values for fields like custom user selects or tags
For custom fields that refer to other Aha records, what record reference to use
An example csv showing how to properly configure different kinds of fields for upload
More informative logs--when records are created but csv columns have data in them that could not be added to certain fields it would be useful to see why
© 2026 Aha! Labs Inc.•All rights reserved
It is also unclear on how to successfully import parents successfully. I've received an error when attempting to add the Parent field to the Objective, even though I'm using the Objective ID of Roll-Up Objective in the workspace line.
it would be helpful if the CSV import menu matched the terminology we have renamed in the tool. For example, we have renamed Features to Product Activities, but in the CSV import menu it still appears as Features. This adds to the confusion and makes for a frustrating user experience.
It would also be helpful to expand on the current fields available for import.