Sales features

Import leads from Excel into your CRM, take your data anywhere

Import leads and contacts into your CRM from spreadsheets, with columns matched for you, duplicates skipped and consent kept honest — then take your records back out as CSV, Excel or JSON whenever you need them, by hand or on a schedule.

  • Leads and contacts in from any CSV
  • Every skipped row explained in a report
  • Exports as CSV, XLSX or JSON, on demand or on a schedule
An example of importing and exporting in DigiPix Flow. A CSV called leads-sept.csv with 2,418 rows is dropped into the import sheet, its columns such as Mobile No and Organisation are matched to lead fields, and the leads import job runs and completes with 2,396 leads imported, 22 rows skipped as duplicates and an error report to download. A deals export then finishes and deals.xlsx is ready to download from the job history.
record types you can export, from leads to segments
6
export formats: CSV, XLSX and JSON
3
a finished export stays ready to download
7 days

What moves in and out

  • CSV filesSpreadsheets from your team, events and old tools
  • LeadsNames, phones, sources and companies, ready to route
  • ContactsPeople linked to the company named in the file
  • Consent columnsEmail, SMS and WhatsApp opt-ins with their evidence
  • Export filesCSV, XLSX or JSON for six record types
  • Scheduled exportsDaily, weekly or monthly files for your admins
THE PROBLEM

Where spreadsheets and CRMs collide

See how it's fixed
  1. Months of enquiries stuck in spreadsheets

    Every rep keeps a sheet of their own, the trade show list sits in someone’s downloads folder, and the agency sends a fresh file every week. Nobody wants to retype 2,000 rows, so the leads never reach the CRM and never get a follow-up.

  2. One bad upload doubles the database

    A list gets pasted in twice, or a column lands in the wrong field. Now Priya Sharma exists three times, phone numbers sit where email addresses should be, and the team spends the next month cleaning up instead of selling.

  3. Data that goes out and is never seen again

    Someone downloads the full customer list to “do some analysis” and it ends up on a personal laptop. Nobody knows who took what, when, or whether the file ever left the building.

UPLOAD

Drop in a spreadsheet and choose what it becomes

Pick whether the file holds leads or contacts, then drop in a CSV. DigiPix Flow reads the file in the browser before anything is saved, lists the columns it found and tells you how many rows it is about to work with. Import covers leads and contacts, the two records that usually start life in a spreadsheet.

  • Import leads or contacts from a CSV file
  • The file is read and checked before anything is saved
  • Row and column counts shown up front
  • Start from the Leads or Contacts list
About CSV import
An example of starting an import in DigiPix Flow: a choice between importing leads or contacts with Leads selected, a drop zone for a CSV file, and the uploaded file leads-sept.csv read in the browser with 2,418 rows and 11 columns, previewing its first three rows before moving on to map columns.
COLUMN MAPPING

Columns matched to the right fields for you

Headers such as Full name, Mobile, Surname, Organisation or Lead source are recognised and matched to the right field without you touching them. Anything the importer doesn’t recognise is shown so you can pick a field or leave it out. The import won’t start until a name, email or phone column is mapped, so every record can be identified.

  • Common header names matched automatically
  • Change any match, or leave a column out
  • Consent source and consent date columns recognised
  • A company column on contacts creates and links the company
See how contacts work
An example of the column mapping step in DigiPix Flow: eleven CSV columns from leads-sept.csv, with Full Name, Surname, Email Address, Mobile No, Organisation and Lead Source matched automatically to lead fields, WhatsApp opt-in, opt-in source and opt-in date matched to consent fields, and City and Budget left out of the import.
JOB HISTORY

Every import and export, tracked as a job

Each import and export runs as a job in the background, so you can keep working while a large file is processed. The job history shows what ran and when, its status and how many rows succeeded or failed, and a notification tells you when your job has finished. Each request carries a retry key, so the same request arriving twice creates one job, not two.

  • Queued, running, completed, partial or failed at a glance
  • Rows imported and rows with problems on every job
  • Re-run an import that failed, stopped or partly worked
  • Import, export, download and re-run written to the audit log
Explore the audit log
An example of the import and export job history in DigiPix Flow: jobs for leads, contacts, deals and companies that are queued, running, completed, partial or failed, each with rows succeeded and rows with problems, one weekly scheduled export, and a contacts import selected with 1,236 rows imported and 28 with problems, a Download error report button and a Re-run button.
ERROR REPORT

A report of every row that didn’t make it

Download the error report for any import and you get one line for each skipped or failed row, with its row number, what happened and why, next to the values that were uploaded. Fix the rows in your spreadsheet and bring them in again. Cells are made safe before the file is written, so a formula hidden in an uploaded row can’t run when someone opens the report.

  • Every skipped or failed row, not just the first few
  • Row number, error code and a plain reason on each line
  • The original uploaded values kept beside the reason
  • Formulas in uploaded cells neutralised in the report
An example of an import error report from DigiPix Flow opened as a spreadsheet: contacts-import-errors-c41d7e92.csv with 28 rows, each giving the row number, whether it was skipped or failed, an error code and a plain reason such as a record with this email already exists or a missing name, email and phone, next to the name, email and phone that were uploaded.
EXPORT

Export CRM data in the format you need

Export leads, contacts, companies, deals, tasks or segments as CSV, Excel or JSON. Narrow the file to what matches your current list filters or a date range, pick the columns, and add notes and follow-ups to lead and contact exports. Exporting needs its own permission, separate from viewing, and a person only ever exports the records their role lets them see.

  • Leads, contacts, companies, deals, tasks and segments
  • CSV, XLSX or JSON files
  • Current filters, a date range and chosen columns
  • Export permission kept separate from view permission
Explore segments
An example of exporting data from DigiPix Flow: a choice of leads, contacts, companies, deals, tasks or segments with Deals selected, a choice of CSV, Excel or JSON with Excel selected, an option to export only what matches the current filters for owner Kavya Iyer, a date range for September 2026, chosen columns, and a finished file deals-export-4b1e9d07.xlsx with 312 rows ready to download for seven days.
SCHEDULED EXPORTS

A fresh file on a schedule, with the controls to match

Set a daily, weekly or monthly export of leads, contacts, companies or deals as CSV or XLSX. Each run lands in the job history, where the file waits for seven days, and the admin who set it up can be notified when it is ready. Admins can mask names, emails and phones in exported files, stamp each file with who exported it and when, and ask people to sign in again before a download.

  • Daily, weekly or monthly, as CSV or XLSX
  • Files kept ready to download for seven days
  • Mask names, emails and phones in exported files
  • Watermark files and ask for sign-in again before a download
See scheduled reports
An example of scheduled exports in DigiPix Flow's import and export settings: a weekly export of leads as Excel, switched on with a notification when the file is ready, showing its next and last run, the workspace's export rules to mask personal details, watermark files and ask people to sign in again before a download, and the last three scheduled runs, two ready to download and one whose file has expired after seven days.
MOBILE APP

Import and export leads from your phone

A list from an event lands on your phone as a CSV. Open it in the DigiPix Flow app, check how the columns were matched and import the leads there and then. From the leads list, export your leads as a CSV and share the file straight from the phone’s share sheet. Larger files are better handled on the web.

  • Pick a CSV on the phone and import leads
  • Columns matched and checked before import
  • Export leads as a CSV file
  • Share the file from the phone’s share sheet
See the lead inbox
An example of import and export in the DigiPix Flow mobile app: a CSV of 184 leads from an expo picked on the phone with its name, mobile, email, company and source columns matched to lead fields and an Import leads button, and a second phone exporting about 486 leads as a CSV that opens in the phone's share sheet.
HOW IT WORKS

From a spreadsheet to clean records, in five steps

  1. STEP 01

    Upload a spreadsheet

    Choose leads or contacts and drop in a CSV to preview it.

  2. STEP 02

    Match the columns

    Common headers are matched for you; adjust or leave out the rest.

  3. STEP 03

    Review and import

    See rows ready, rows needing attention and consent warnings, then run the job.

  4. STEP 04

    Check the job

    Follow its status, download the error report and re-run if needed.

  5. STEP 05

    Export when you need it

    Download CSV, XLSX or JSON now, or set a schedule for a fresh file.

THE DIFFERENCE

Import & export vs copy-paste and one-off scripts

What it coversCopy-paste and one-off scriptsDigiPix Flow
Getting a spreadsheet inRows retyped, or pasted in and hoped forCSV upload with columns matched and previewed first
Records already in the systemCopied again, then cleaned up by handRows with an existing email skipped automatically
Consent in the fileIgnored, or trusted without questionOpt-outs always applied, opt-ins only with source and date
Rows that failLost without a traceAn error report with each row, its reason and its values
Knowing what happenedWhoever ran the script remembers, maybeA job history, notifications and audit log entries
Getting data outScreenshots and copy-paste from list pagesCSV, XLSX or JSON for six record types, by filter or schedule
Protecting what leavesAnyone with access can pull the whole listSeparate export permission, masking, watermarks and sign-in again
INTEGRATIONS

How files reach DigiPix Flow

CSV import is how spreadsheets reach DigiPix Flow: leads and contacts in, with columns matched and duplicates skipped. The same page takes records back out as CSV, XLSX or JSON, so nothing you put into the CRM is locked inside it.

Import and export questions, answered

What can I import?

Leads and contacts. Lead imports set the name, email, phone, company name and source, and contact imports set the name, email, phone, job title, lifecycle, tags and company. Both can carry email, SMS and WhatsApp consent columns.

Which file types does import accept?

Import reads CSV files. If your list lives in Excel, save it as CSV first. Exports come out as CSV, XLSX or JSON.

How are my spreadsheet columns matched to fields?

Common header names are recognised automatically, so Mobile, Phone number or Contact number all become Phone, and Surname becomes Last name. You can change any match or leave a column out before you import.

What happens to people who are already in the CRM?

A row whose email address already belongs to a lead or contact is skipped rather than copied, and it appears in the error report with the reason. If that row carries an opt-out, the opt-out is still applied to the existing record.

How is consent in an import file handled?

Opt-outs are always applied. An opt-in is only recorded if your workspace has chosen to accept consent from import files and the row also has a consent source and a consent date that isn’t in the future. Otherwise the opt-in is stored as unknown, so a file can’t give permission on its own.

What if some rows fail?

By default the job keeps going past a bad row and finishes as partial, with every good row imported. Download the error report to see each failed or skipped row with its reason and the values you uploaded, fix them, and import them again. A failed or partial import can also be re-run from the job history.

Can I bring data over from my old CRM?

There is no direct connector to other CRMs. Export your leads and contacts from your current tool as CSV files and import them here, with columns matched and duplicates skipped.

Who can export data, and is it recorded?

Exporting needs its own permission, separate from viewing records, and a person only exports what their role lets them see. Each export request and each download is written to the audit log, and admins can mask personal details, watermark files and require signing in again before a download.

How do scheduled exports work?

An admin chooses leads, contacts, companies or deals, a daily, weekly or monthly cadence and CSV or XLSX. Each run appears in the job history with a file to download for seven days, and the admin who set it up can be notified when it is ready.

Can my team import and export on their phones?

Yes, for leads. The mobile app imports leads from a CSV on the phone and exports leads as a CSV file to share. Bigger files are best imported on the web.

Something we haven't covered? Talk to an expert

Bring your spreadsheets. Leave with clean records.

Talk to an expert — bring a sample of your lead list and see it matched, checked for duplicates and imported, then exported back out.

  • A real person, not a bot
  • Bring a sample of your list
  • See it imported before you decide
Talk to an expert