Keap migration
Bring the history, not just the contact list.
Switching from Keap usually means a CSV of contacts and a shrug about everything else. MADDOX connects to your Keap account and walks it: contacts, companies, opportunities, tags, notes, tasks, appointments, emails, orders and files, with each historical item placed on the timeline at its original date. You decide how Keap’s pipeline, tags, fields and people map across in a six-step wizard before anything is written. It is a guided import rather than a zero-touch one: Keap accounts are set up in very different ways, so you review the map, run it, and check a sample of records before you rely on it.
How it works
From a Keap key to a populated CRM
Nothing is written until the last step of the wizard, and every step after that can be stopped, resumed or undone.
Connect your Keap account
Paste a Keap service account key. MADDOX makes one cheap test call to prove the key works before saving it, and tells you plainly when Keap rejects it.
Map it in six steps
Pipeline and stages, tags and lists, fields, people and lead sources, options, then review and run. Suggestions are offered only where there is real evidence for them, and the last step lists anything still unanswered rather than letting you click past it.
Run it, check it, resume it
The import runs in the background and counts up record by record. If it stops — Keap’s rate limit, a closed laptop, anything — it resumes from where it got to rather than from the top, and a re-run never duplicates what is already there.
In the product
The mapping wizard, with every suggestion marked as one.
The wizard
Six steps, decided once, saved for next time.
A Keap account carries years of somebody’s choices about tags and fields. The wizard is where you decide which of them still mean something.
What each step asks.
The six steps, in order:
- Pipeline and stages — which MADDOX pipeline Keap opportunities land in, and which stage each Keap stage becomes, including the won and lost outcomes
- Tags and lists — which Keap tags carry across as tags, and which become something more useful
- Fields — where each Keap custom field goes: an existing property, a new one, or merged into another
- People and sources — which Keap users are which MADDOX users, and how Keap lead sources map onto your own lead-source values
- Options — what the run should and should not bring across
- Review and run — everything you chose, and anything you have not answered yet
Suggestions are visible as suggestions.
A pre-filled wrong answer, accepted by somebody in a hurry, is never found again. So a stage suggestion is offered only when there is evidence — a stage already carrying that Keap id, a won or lost stage matching the outcome, or a strong name match — and every suggested row stays visibly a suggestion until somebody touches it. The whole map is saved in one go at the end, so stepping back to fix a stage never leaves half a map behind.
Templates, so the second run is not a second afternoon.
Save the map as a template and apply it later, to a re-run or to another workspace with the same Keap setup. The wizard shows what a template filled in and what it left for you, so a template never quietly answers a question it did not know about.
What comes across
Records, history and the reasons not to email somebody.
Records and history, on the timeline at their real dates.
Contacts and companies come across as records. Opportunities become deals in the pipeline you mapped. Tags, lead scores and custom field values follow their mapping, and files are downloaded into MADDOX’s own storage rather than left as links back to Keap.
History is the part a CSV cannot carry. Notes, tasks, appointments, applied tags, emails, orders and opportunity stage moves each land on the contact’s timeline dated when they happened in Keap, so a contact’s last five years read in order alongside whatever your team does next. Anything the importer does not explicitly map is kept with the record in its raw form rather than thrown away.
Opt-outs and bounces carry over.
A contact who unsubscribed in Keap, or whose address hard-bounced there, is carried into the same suppression ledgers every MADDOX send consults. An opt-out and a bounce are recorded as different things, because one is the contact’s choice and the other is a fact about the mailbox. The first campaign you launch after switching does not email somebody who asked you to stop.
Keap campaigns arrive as drafts to review.
A Keap campaign can be brought across as a draft journey: one lane per sequence path, with goals wired the way Keap wired them and timers parsed from their descriptions. Keap’s API does not expose campaign email bodies, so email steps arrive with placeholder copy flagged for review, and steps MADDOX cannot safely run become notes recording what they were for. Nothing sends until you have rewritten it and launched it yourself.
TurboDial calls
Your calling history, transcribed and graded.
For MSP teams that dialled out of Keap, the calls are often the most valuable history in the account.
Import a date range of calls.
The call import works the other way round from the contact migration: it asks Keap what calls happened in a window and works back to the people, so a call to somebody who was never migrated is not missed. Before it starts, you confirm which Keap user each caller was, and the import will not begin until a person has confirmed that mapping.
Every call keeps its own time, and recorded calls are transcribed.
Each call, its recording and its timeline entry carry the time the call was made, not the time the import ran. Recorded calls are matched to their audio, transcribed and graded by MADDOX like any other call, so the coaching and performance views have your history to work from on day one. A call with no recording says so and gets no grade, because there is nothing to grade.
Run the same range again and nothing is duplicated; what was missing — a recording that was not there last time, a transcript that failed — is filled in. That is the point of a re-run.
Undo and honesty
A migration you can take back out, and what we will not promise.
A scoped delete that only removes what the import created.
If the first run was mapped wrong, you can remove everything the Keap import created and run it again. The delete is decided by provenance alone — a marker the importer wrote on each row — never by date range. A contact your team has since logged a call against, or a deal somebody added a note to, is skipped rather than deleted, and every skip is counted and reported.
Each call-import run can also be removed on its own, without touching the contact migration.
What a guided import cannot do for you.
Keap accounts differ, and Keap’s own API is not equally clear about every field, so the importer reads defensively and keeps the raw data rather than guessing. That is why the honest instruction is: map it, run it, then open a handful of contacts, deals and calls and check them against Keap before you switch your team over. Delivery outcomes for emails sent from Keap are not part of what Keap hands over, so imported emails show as sent with delivery unknown rather than as delivered.
And if you ever leave MADDOX.
The way out matters as much as the way in. Records export to CSV from their own screens, larger exports run in the background and can be scheduled, and any single contact’s data can be exported in one file. What you can export if you switch platforms, recordings included, is answered in full on its own page.
Who it is for
For MSPs that outgrew Keap
Keap is a small-business marketing tool. An MSP selling managed IT on contracts needs deals, calls and coaching at the centre of the CRM rather than around the edge of it.
- MSP owners looking for a Keap alternative without losing years of history
- Teams that dialled through TurboDial and want those calls to count
- Whoever has to run the migration and be able to undo it if the first map was wrong
Related
Questions
The things people actually ask.
Is MADDOX a good Keap alternative for an MSP?
If you sell managed IT on contracts and live on the phone, yes — that is who it is built for. You keep your Keap history, your TurboDial calls are transcribed and graded, and the pipeline, call recording and coaching are built around how an MSP actually sells.
How long does migrating from Keap take?
It depends on the size of the account and Keap’s rate limits, which is why the import runs in the background, counts up as it goes and resumes where it stopped. Plan time for the mapping and for checking a sample afterwards; that part is yours.
Is the Keap import fully automatic?
No, and we would rather say so. It is a guided import: you map pipelines, tags, fields and people in a six-step wizard, the run itself is automatic, and then you check a sample of records against Keap before switching your team over.
Can I undo a Keap import?
Yes. A scoped delete removes only rows the Keap import created, skips any record your team has since added work to, and reports what it skipped. Call-import runs can be removed one at a time.
Do my Keap email campaigns come across?
Their structure does, as draft journeys you review. Keap does not expose campaign email bodies through its API, so those steps arrive with placeholder copy flagged for review, and nothing sends until you launch it.
Map your Keap account before you commit to anything.
Connect it, walk the six steps and read the review screen. Nothing is written until you press run, and a wrong first map can be taken back out.