Reporting and data

Data Hub imports

Map CSV columns into supported records and preview what will change.

How it works

Preview a CSV mapping before records change

Map incoming columns to supported records and inspect the planned changes before import. Reusable team mappings and correction files make repeat imports easier to manage.

01

What it covers

Save team mappings, download correction files, review import history and use conflict-aware rollback.

02

In practice

Review import history and use conflict-aware rollback when supported.

When to use it

Useful situations

  • Preview a customer CSV before records change.
  • Save a team mapping for a regular supplier export.
  • Correct rejected rows and use supported rollback carefully.

A working path

How the work moves

  1. Map

    Match CSV columns to supported record fields and inspect the preview.

  2. Import

    Confirm the validated batch and retain the import history.

  3. Recover

    Download correction information or use conflict-aware rollback where offered.

Illustrative scenario

contact migration

An administrator previews contact fields, fixes invalid email rows and imports the remaining records using a saved mapping. The preview separates rows ready to import from rows that need correction, giving the administrator a chance to fix mappings and required values before customer records are created or updated.

Before you start

What to check

  • Imports support defined record types and fields only.
  • Rollback avoids silently overwriting changes made after the import.

Questions about Data Hub imports

Useful details before you start.

All questions
Can we undo every import?

Supported imports provide history and conflict-aware rollback where applicable.

Can mappings be reused?

Yes, team mappings can be saved for supported import workflows.

Get started

See your customer work in one place.

Start with the core CRM for free, then add the tools your team needs.