“How do you import leads without discovering the damage three weeks later?”

Lead import and migration

A mapped import that shows exactly what it will create, update and reject before it writes anything.

Why imports go wrong quietly

The usual import is a mapping screen and a button. It reports a row count, everybody moves on, and three weeks later somebody notices four hundred records with a blank owner or a date field that landed as text.

By then the bad data has been worked on, so undoing it is no longer simply a matter of deleting what arrived.

Map the CSV to fields, and the import produces a diff before it writes: rows to create, rows to update field by field, rows matched as duplicates, and rows rejected with the reason.

Nothing commits until that is approved, and the commit is a single audit entry — so what the import actually did is answerable later.

How the path works

What changes on arrival

Duplicate detection runs inside the import, so a returning contact joins their existing record rather than becoming a second one with a second owner.

Routing rules assign what arrives, so imported leads have an owner and a clock rather than sitting in a bulk-loaded pile nobody feels responsible for.

Moving your pipeline in takes four days.

Other journeys

Lead import and migration, answered.

Bring the journey that hurts most.

We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.