Skip to main content

A one-time batch, not a live sync

Load Testimonials Into CRM by CSV

Sales wants to see, on the contact record, that this customer once wrote you a glowing testimonial. You do not need an integration for the testimonials you already have: one CSV export, a little shaping, and the CRM’s own import tool will do it. The checklist below prepares the file around the question a CRM import turns on: how each row finds the right contact.

  • Shape the export around the CRM’s matching key
  • Map testimonial text to a property you created
  • Test ten rows before importing the rest

The problem, solved

What makes a testimonial backfill into a CRM go wrong

CRM steps below follow HubSpot’s help article as read on 2026-11-19. Other CRMs have their own import screens.

  • The testimonials are in another tool

    Copying quotes into contact records by hand is slow and invites typos in a customer’s own words.

  • The import created duplicate contacts

    If rows cannot be matched to existing contacts, the CRM creates new ones, and sales sees two records for one customer.

  • Sales quoted something we never approved

    Rejected or pending submissions in a CRM look like proof to a rep in a hurry.

  • Only some testimonials matter to sales

    A rep needs the quote about the product they sell, not every message in the library.

  • Next month the CRM is out of date

    A one-time import stops the day you run it, and new testimonials pile up outside the CRM again.

Flip the switch to see how StoryProof handles each one.

File preparation

Prepare the testimonial file for your CRM

Each item protects either the contacts sales relies on or the customer’s words. Tick them before you open the CRM’s import screen.

Decide in the CRM first
Shape the export
Import safely

This list works offline in your browser. It does not connect to any CRM.

Mapping decisions for a testimonial import

Columns depend on what your export holds. Inspect it and decide each one.

If your file hasMap it toWatch for
The customer’s emailThe CRM’s contact key (Email in HubSpot)Blank cells create unmatched rows
The testimonial wordsA new property made for testimonialsText length limits in the CRM field
A ratingA number property, or skip itSales reading stars out of context
A dateA date propertyFormat that the CRM accepts
Anything sales does not needDo not import columnKeep the import narrow

In StoryProof

Backfill your CRM in one batch

  1. 1

    Export and trim

    Download the space’s CSV, keep approved testimonials only, and make sure each row carries the contact key.

  2. 2

    Start the CRM import

    In HubSpot, click Import on an object index page, or go to Data Management, Data Integration and choose Import data. Pick contacts and how to import: create and update, create only, or update only.

  3. 3

    Map the columns

    Map the email column as the unique identifier, the testimonial text to your new property, and set Import As to Do not import column for anything else. Resolve any mapping errors the screen lists.

  4. 4

    Test, then run the batch

    Import ten rows, open the matched contacts, then import the rest with a dated import name.

  5. 5

    Keep it current

    New testimonials after the backfill can travel by webhook, from Pro.

What happens next: Tell sales which property holds the quote and that it only contains approved testimonials.

Before you start

Limits and assumptions

What this does not cover, and what to check on your side. Better to know now than after launch.

  1. 01

    CRM steps as of 2026-11-19

    The HubSpot path follows its knowledge base article read on 2026-11-19 and was not tried on a live account. Other CRMs differ; follow their own import help.

  2. 02

    Export fields are not promised

    This page does not say the export contains an email column or any particular field. Inspect it and fill gaps from your own records.

  3. 03

    No native CRM connector is claimed

    StoryProof is not described here as syncing with any CRM. The CSV import and webhooks are the routes.

  4. 04

    Consent covers marketing use

    Customers agreed to a testimonial, not necessarily to sales quoting them in one-to-one emails. Check your permissions before reps reuse quotes.

FAQ

Questions people ask

Short answers to what usually comes up next.

Should testimonials be a note or a property on the contact?

A property is easier to filter and report on. HubSpot also notes that existing notes cannot be updated by import, so a property is simpler to correct later.

Will this overwrite fields sales already filled in?

Only if you map a column onto one. Map testimonial text to a new property made for it and skip everything else.

Do I need a paid StoryProof plan to export?

The CSV export lives in the workspace settings, and testimonials stay exportable after the trial ends even without a paid plan.

Can I repeat the import every quarter instead of using webhooks?

Yes, as long as each run is keyed to the same contact identifier and writes to the same property. Webhooks only save you the manual step.

Still have a question? Ask the StoryProof team or book a demo.

Collect once, use it in every tool

Keep the library in StoryProof and export a space whenever another system needs the rows.

Sources

  1. Import records and activities, HubSpot Knowledge Base. Checked 2026-11-19.

Last updated 2026-11-19.