Home / Features / Import and export
Feature

Your supplier list should
move in and out freely

A workspace that is hard to get data into does not get adopted, and one that is hard to get data out of should not be. Both directions matter, and the second one matters most when you are deciding whether to start.

Import from almost any fileExport with scores attached
Both directions matter

Getting in is adoption, getting out is trust

Teams evaluate import because it decides whether starting is painful. They should evaluate export because it decides whether leaving is possible.

Outcome

You can start with the list you already have

No reformatting into somebody else's template, no cleaning it up first. Bring the file as it stands and the mapping is suggested for you.

In practiceStarting takes an afternoon rather than a data project.
Outcome

The list does not double

Suppliers already held are matched and skipped during import, which is the single most common way a vendor master gets worse rather than better.

In practiceOne record per supplier, not two.
Outcome

Approved suppliers move onward

Once a supplier is qualified, the record can be exported with scores, categories and document links, or pushed onward to the systems that need it.

In practiceQualification feeds your buying rather than sitting beside it.
How data usually moves

And where the friction actually is

Import is the part everyone asks about. Export is the part worth asking about.

Book a demo
The challenge

Reformat to their template

The tool accepts one shape of CSV, so somebody spends a morning reshaping columns before anything can be tried at all.

AcceptedOne format
PreparationReal
Trying itDelayed
With VendorHub

Bring it as it is

CSV, Excel, PDF, Word or an image, with mapping suggested rather than demanded.

AcceptedMost formats
PreparationMinimal
Trying itImmediate
The challenge

Exact match or nothing

A column called categorie instead of category fails the import, and somebody has to work out which of forty columns caused it.

MatchingExact
Near missesFail
DebuggingYours
With VendorHub

Matched intelligently

Close column names are matched and shown to you for confirmation before anything is imported.

MatchingFuzzy
Near missesSuggested
DebuggingRare
The challenge

Imported anyway

The file contains suppliers you already hold and they arrive as second records, which is how a master file quietly doubles.

DetectedNo
ResultDuplicates
CleanupLater, manually
With VendorHub

Detected and skipped

Existing suppliers are matched during import and skipped, with the count shown before you commit.

DetectedYes
ResultClean
CleanupNot needed
The challenge

Awkward by design

Export is limited, partial, or a support request, which is a commercial decision dressed as a technical limitation.

ExportLimited
Includes scoresNo
LeavingHard
With VendorHub

Straightforward

The directory exports with scores, categories and document links included, by file or onward via API.

ExportFull
Includes scoresYes
LeavingPossible
Questions we get asked

About import and export

What formats can we import from?
CSV, Excel, PDF, Word and image files. The point is that you bring the file you already have rather than reformatting it into a template first.
What if our column names do not match?
They are matched intelligently, including near misses such as categorie for category, and the suggested mapping is shown for confirmation before anything is imported.
How are duplicates handled?
Suppliers you already hold are matched during import and skipped, with the count shown beforehand. That is what stops an import doubling your master file.
Can we export our data?
Yes, in full, with EP Scores, categories and document links included. We would encourage you to test this during an evaluation rather than after.
Can approved suppliers be sent to another system?
Yes, by export file or onward via API, so qualification feeds the systems that handle buying and payment rather than sitting separately.
Does importing suppliers score them?
Imported suppliers become records in the directory. Scoring draws on public records, so an imported supplier can be scored without re-onboarding them from scratch.
Is there a limit on import size?
Not one most teams encounter. Larger files are processed with the same mapping and duplicate detection.
Related

Other parts of the workspace

FEATURE

Clean up a messy vendor list

What a first import of a legacy list actually looks like.

Read more
FEATURE

Vendor directory

Where imported suppliers land.

Read more
FEATURE

Security and data handling

How your data is handled while it is with us.

Read more

Bring your messiest export

We will import a sample on the call and show you the duplicate count before anything is committed.