Skip to main content

Switching survey platforms

Keep all your survey data in one place when you switch to Grapevine

Written by Steve Jones

Switching survey platforms usually comes with a worry: what happens to everything you have already collected? You have months, maybe years, of responses on the old platform, and you do not want to lose that history the moment you move across.

Here is what we recommend. Rather than importing your old responses into Grapevine Surveys, keep a backup of them as a CSV and bring them into a project inside your own AI assistant. Then connect Grapevine to the same place. Your past responses and your live Grapevine data sit side by side, and you can ask questions across all of it in plain language.

Why we do not recommend importing historic responses into Grapevine

It sounds tidy to load everything into one dashboard, but it causes a real problem with your reporting.

Grapevine calculates response rates from how many customers were shown a survey against how many answered it. Imported responses have no impression behind them, so they land in your reporting as though every single person asked gave an answer. Your response rate gets pulled towards 100% and stops telling you anything useful about how your live surveys are actually performing.

Keeping the two separate avoids that. Grapevine reports on what Grapevine collected, cleanly and accurately, and your historic data stays exactly what it is: a record of what happened before you switched.

Why an AI project is the better home for it

We think this is genuinely the better way to work now, not just a workaround.

Your old platform's dashboard was only ever able to answer the questions it was built to answer. Once your historic export sits in an AI project, you can ask it anything, in your own words. And with Grapevine connected to the same assistant, you can ask questions that span both sets of data at once, without exporting anything or flipping between two tools.

You keep a clear line between historic and live data, your reporting stays honest, and you still get to look across the whole picture whenever you want to.

What you will need

  • An account with an AI assistant that supports projects and connectors, such as Claude or ChatGPT

  • An export of your historic data from your previous survey platform, usually a CSV file

  • Your Grapevine account, ready to connect to your AI assistant

Recommended steps

Export your data from your old platform

Before you move off your previous tool for good, download your response data. Most platforms let you export to CSV or a spreadsheet from their reporting or settings area. Take everything you want to keep.

Do this while you still have access to the account. Once a subscription lapses, getting your data back is often difficult and sometimes impossible.

Store a backup somewhere safe

Save a copy of those CSV files somewhere you control, such as Google Drive, Dropbox, or your own machine. Somewhere you would still be able to find them in a year.

This is your master copy. Everything else you do with the data is a working copy, so if a project gets deleted or you want to start again, you have the original sitting safely. It takes two minutes and it means your survey history is genuinely yours, not tied to any platform.

Create a project in your AI assistant and add your export

In Claude or ChatGPT, create a new project for your survey data. Give it a clear name like "Customer Survey Data" so it is easy to come back to.

Add your exported files to the project so the assistant can read them. This becomes the home for your history: the record of everything you collected before the switch.

Connect Grapevine to the same AI assistant

Now connect Grapevine so your live survey data is available in the same place. This uses Grapevine's AI connection, which lets you query your survey data straight from Claude or ChatGPT without exporting anything.

For the full walkthrough, see our guide on connecting your survey data to AI tools like Claude or ChatGPT.

Once Grapevine is connected, your assistant can pull your current responses on demand, right alongside the historic files you already added.

Now you can ask questions across everything

With your past data in the project and Grapevine connected live, you can treat the whole lot as one dataset while keeping the two clearly labelled. A few things you might ask:

  • How does our attribution mix now compare with the same months last year?

  • Which channel has grown the most since we switched platforms?

  • Show our NPS trend across both the old data and our live Grapevine responses.

  • What were customers saying about delivery before, and are they still saying it now?

No more comparing an old dashboard against a new one by eye. It is all in one place, ready to answer whatever you ask.

A tip for keeping it tidy

Label your historic files clearly, by platform, date range, and survey type, so you and your assistant can always tell old data from new.

Something like delighted-nps-2024-2025.csv will do the job.

A little structure up front makes every question you ask later easier to answer, and it keeps the distinction between historic and live data obvious in every answer you get back.

Need any help?

If you have any questions about migrating your existing survey data over to Grapevine Surveys, or any other Grapevine Surveys related question, then please do just get in touch.

Did this answer your question?