I loaded my historical data into the same project to preserve the data and the ability to map trends for the dashboards.You can always add a metadata field to define your responses by region to allow additional filtering as an option. As for worrying about something going wrong: I typically create a clone of the project when I am loading data. If the load goes well, I make the new “primary” project. If it doesn’t go well, you can delete and start over. Working iteratively allows for more attempts without damaging the overall project.

You can always add them as their own project and map them into the dashboard as additional datasources if there are too many concerns about overlap and messy data.

Hello @Erikahuer,

If the historical surveys share the same questions, I’d suggest combining them all together into a single dataset so you only import responses once instead of 8 times, then import into Qualtrics as a separate dataset from the new survey one, and you can then join them together on the dashboard itself.

This would help you to keep historical responses clearly separated from those coming from the new survey (you can create a Live/Historical flag that can be used as filter on the dashboard if needed), yet at the same time enable you to report on trends and aggregated calculations using all the data together.

Best,

Daniel