Switching tools
Migrate Testimonials From Another Tool
A plugin announces its end date, or a subscription renewal arrives for a tool you have outgrown. The testimonials are the part you cannot recreate, and they are scattered across an export file, a video folder, embed code on a dozen pages and collection links in old emails. Work through the checklist so nothing is left behind when the old tool switches off.
- Everything to save before the old tool closes
- Mapping, videos, embeds and links in order
- A summary to copy into your project notes
The problem, solved
What gets lost in a tool switch, and how StoryProof picks it up
The export file has its own column names
Every tool labels its fields differently, and some exports add internal ids and status columns you do not need.
With StoryProof: Upload the CSV and match its columns to name, testimonial text, rating, company, job title and date. Only the name has to be present.
Our video testimonials will vanish with it
A CSV carries words, not recordings. If the videos stay in the old tool, they disappear on the shutdown date.
With StoryProof: Download the video files while you still can, then upload them directly into StoryProof.
Old widgets will break on live pages
Embed code from the old tool is spread across the homepage, pricing page and landing pages. When it stops loading, those sections go blank.
With StoryProof: A StoryProof widget is two lines of HTML, a div with the widget id and the embed script, and one copy of the script in a shared footer can serve every widget on a page.
Customers still click the old request link
Collection links sit in email signatures, onboarding sequences and printed inserts, and will lead nowhere once the old tool closes.
With StoryProof: Replace them with a StoryProof collection link where customers can record a video, leave an audio note or write a few lines.
Years of quotes, not all still true
A migration moves everything at once, including praise for retired features and customers who have since left.
With StoryProof: Imported testimonials wait in the approval queue instead of going public, so you can leave outdated ones unpublished and tag the rest.
Flip the switch to see how StoryProof handles each one.
Switching checklist
Everything to move before the old tool closes
Work top to bottom. Tick each item as it is done; the summary lists what is still open.
Ticks are stored in your browser only and never sent.
What moves, and how
This plan relies only on files you export yourself, so it works whichever tool you are leaving.
In StoryProof
The move, in order
- 1
Import the CSV
Upload the export and map its columns. Leave internal ids and status fields unmapped.
- 2
Upload the videos
Add each saved video file to StoryProof so recordings sit beside the written testimonials.
- 3
Approve and tag what is still current
Go through the queue, approve testimonials that still describe your product, and tag them for the pages they belong on.
- 4
Build widgets for each page that had one
Choose the testimonials for each widget, then swap the old embed code for the StoryProof div and script.
- 5
Swap the collection links
Replace the old request link in templates, signatures and onboarding emails with your StoryProof link.
What happens next: Keep the original export and video folder after the switch. If a question about a testimonial’s source comes up later, they are your record.
Before you start
Before you start the move
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
Your export decides what moves
This route uses the old tool’s export file. What you can bring across depends on what that tool lets you download.
- 02
Imports use your monthly allowance
Imported testimonials count toward the same monthly limit as collected ones. A large archive may need a bigger plan for the month you move.
- 03
Permissions do not travel in a CSV
Consent records stay your responsibility. Keep them with the export, and ask again if you are unsure what a customer agreed to.
- 04
Old embeds must be removed by hand
StoryProof cannot remove another tool’s script from your site. Leftover code can slow pages or show empty boxes.
- 05
The deadline is the old vendor’s
Check their notice for the exact shutdown date and whether data stays downloadable afterwards. Do not assume it does.
FAQ
Questions people ask
Short answers to what usually comes up next.
My testimonial plugin is being discontinued. What do I do first?
Export everything while it still works: the testimonials as a file, and every video and image. Everything else can be rebuilt afterwards; lost data cannot.
How do the testimonials get from the old tool into StoryProof?
Through files. Export a CSV from the old tool and upload it, then upload any video files separately.
What if my old tool has no CSV export?
Ask its support team for an export before the shutdown. If none exists, copy the testimonials into a spreadsheet yourself and save that as a CSV.
Will my site lose its testimonials during the switch?
Not if you build the StoryProof widgets first and swap the embed code page by page. Remove the old code only once the new widget shows.
Do imported testimonials go live straight away?
No. They wait for approval like anything else, so you can choose what is still current before anything appears on your site.
Still have a question? Ask the StoryProof team or book a demo.
Move before the lights go out
Import your export file, upload your videos and rebuild your widgets in one place.
Last updated 2026-11-05.