Testimonial import: the 4 methods, the 5-step CSV process, and the 4 compliance considerations

Testimonial import is the process of moving existing customer testimonials into a new tool or website. The 4 methods are CSV import, API import, social media scraping, and tool-to-tool migration.

The right method depends on where the testimonials currently live, how many there are, and what format they are in. The import is the fastest path to a populated wall. The import is also riskier than ongoing collection, because the data has quality issues that the team did not generate.

This page is the import. The how to collect testimonials page is the collection process. The testimonial forms page is the form-based collection. The import testimonials from Twitter and LinkedIn page is the social-specific path.

The testimonial questions page is the question patterns. This page is the broader import question: the 4 methods, the 5-step CSV process, the 3 validation checks, and the 4 compliance considerations.

What testimonial import is, and what it isn’t

Testimonial import is the one-time operational task of moving existing customer testimonials from one place to another. The source can be a spreadsheet, a previous tool, social media, an email export, or a CMS. The destination is the new tool or website. The import is the bridge between where the testimonials are and where they need to be.

Testimonial import is not testimonial collection. Collection is the ongoing process of asking customers and gathering new testimonials. Import is the one-time process of moving existing ones. The two are complementary, not interchangeable. A team that imports 50 testimonials and never collects again has a wall that goes stale.

Testimonial import is also not testimonial scraping. Scraping is pulling testimonials from public sources without permission. Importing is moving testimonials the team already has permission for. The compliance story is different. The compliance considerations are real on both, but scraping carries legal risk that import does not.

The 4 import methods

The first method is CSV import. The team exports testimonials as a CSV file. The columns match the destination tool’s schema. The team uploads the CSV. The tool parses the file and creates the testimonial records. CSV is the universal format. Every testimonial tool supports CSV. CSV is the fallback for every other method.

The second method is API import. The team uses the destination tool’s API to create testimonial records programmatically. The team writes a script or uses a connector tool (Zapier, Make) to pull from the source and push to the destination. API is the fastest method for large imports (100+ testimonials).

The third method is social media import. The team pulls testimonials from Twitter, LinkedIn, Facebook, Instagram. The team can do this manually (copy-paste each one) or with a tool that does the scraping. The social-specific path is documented in detail in the import testimonials from Twitter and LinkedIn page.

The fourth method is tool-to-tool migration. The team moves from one testimonial tool to another. The source tool has an export feature. The destination tool has an import feature. The migration is direct. The team uses this method when switching tools (e.g., from Senja to a new platform, from Testimonial.to to a new platform).

For the prompts to use when the imported testimonials lack detail, see the testimonial questions.

The 5-step CSV import process

Step 1 is to export from the source. The team exports the testimonials as CSV from the current tool, the spreadsheet, or wherever the testimonials live. The export includes all available fields: name, role, company, testimonial text, rating, photo URL, date, consent record.

Step 2 is to map the columns. The team opens the CSV in a spreadsheet (Google Sheets, Excel). The team checks that the column names match what the destination tool expects. The team renames columns if needed. The team fills in missing fields where possible (name, role, company are usually extractable).

Step 3 is to clean the data. The team removes duplicates. The team fixes typos. The team standardizes company names (“Acme Inc.” vs “Acme” vs “ACME”). The team checks that the testimonial text is not empty. The team checks that consent is recorded for each testimonial.

Step 4 is to upload to the destination. The team uploads the cleaned CSV to the new tool. The tool parses the file. The tool shows a preview. The team reviews the preview. The team confirms the import.

Step 5 is to verify the imported testimonials. The team checks that the testimonials appear correctly on the wall. The team checks that the photos load. The team checks that the dates are correct. The team fixes any issues that the import introduced.

The 3 import validation checks

The first check is field completeness. The team verifies that every imported testimonial has all required fields (name, role, company, testimonial text, rating). The team flags the testimonials that are missing fields. The team either fixes them in the new tool or removes them.

The second check is photo URL validity. The team verifies that the photo URLs in the import actually resolve to real images. The team flags the testimonials with broken photos. The team either fixes the URLs or removes the photo field.

The third check is consent record presence. The team verifies that each imported testimonial has a consent record. The team flags the testimonials without consent. The team either reaches out for consent retroactively or removes the testimonial from publication.

The 3 common import failure modes

The first failure mode is the missing consent. The team imports testimonials that were collected without a consent checkbox. The team publishes them. The team gets a complaint. The team takes them down. The fix is to audit for consent before importing, and to remove or request consent for the missing ones.

The second failure mode is the broken photo URL. The team imports testimonials with photo URLs that point to the source tool’s CDN. The source tool deactivates the CDN. The photos disappear. The fix is to download the photos and re-upload them to the destination tool’s CDN before importing.

The third failure mode is the lost attribution. The team imports testimonials and the role or company is missing. The wall has unattributed quotes. The credibility is reduced. The fix is to verify the CSV before import and to fill in missing fields where possible.

For the top-6 ranked alternatives as the destination, see the best testimonial software.

The 4 things to do after import

The first thing is to verify the wall looks correct. The team visits the wall page. The team checks that the testimonials display correctly. The team checks that the photos load. The team checks that the schema markup is applied.

The second thing is to tag the imported testimonials. The team adds tags (industry, use case, product feature) so the filter works correctly. The team adds the date (when the testimonial was originally collected, not when it was imported). The team categorizes for the search and filter.

The third thing is to set up the ongoing collection. The team turns on the form. The team sends the first batch of personal asks. The team builds the new collection pipeline that will keep the wall fresh after the import.

The fourth thing is to archive the source data. The team keeps the source CSV for 90 days. The team deletes the source after that. The archive is the safety net in case something goes wrong with the import.

The 4 compliance considerations

The first consideration is the consent record. The team imports only testimonials with a consent record. The team does not import testimonials without consent. The team reaches out to customers for retroactive consent if needed. The consent record is the legal floor.

The second consideration is the data minimization. The team imports only the fields the wall displays. The team does not import phone numbers, addresses, or other PII. The minimization reduces the risk if the imported data is ever breached.

The third consideration is the right to be forgotten. The customer who asks to be removed must be removed from all systems: the new tool, the archive, the source tool (if the team still has access). The team has a process for the removal request that touches every system.

The fourth consideration is the cross-border transfer. If the source testimonials are from EU customers and the destination tool is US-based, the transfer may require GDPR-compliant mechanisms. The team checks the destination tool’s GDPR posture before importing.

The journey after this page

If you have the import and want the broader collection process, the how to collect testimonials page is the parent reference. For the form-based collection (the ongoing side), the testimonial forms page is the dedicated reference.

For the social-specific import (Twitter, LinkedIn), the import testimonials from Twitter and LinkedIn page is the dedicated reference. For the question patterns to put in the testimonial field once imported, the testimonial questions page is the prompts reference.

For the destination tool, the testimonial software page is the category overview. The best testimonial software page is the top-6 roundup. The free testimonial tools page is the free-tier view.

For teams that want to import existing testimonials into a tool that supports CSV, API, and direct tool-to-tool migration from the major competitors, Testivo is one tool that supports all four import methods. The import is the bridge. The tool is the destination. The validation is the safety net.

For the category overview that lists the destination tools, see the testimonial software.

When importing historical testimonials, you may need to request retroactive consent if the original collection did not capture it properly. See what to do with old testimonials without documented consent for the migration paths.

Aggregation is the ongoing version of the import workflow covered in the testimonial aggregator guide.