AI Features & Bots
AI Website Chatbot
Adds a branded AI assistant to your website trained on your content.
Extensions
Data Migration from Existing Bot
Your current bot's flows, FAQs and conversation history move into the new agent instead of being rebuilt from memory.
Switching chatbots should not mean rebuilding years of FAQs and flows from memory. This add-on moves flows, FAQs and conversation history from your current bot or tool into your new Upmark Labs agent. Content is exported, cleaned of duplicates and outdated answers, mapped to the new agent and checked against the old answers before anything goes live.
- Moves flows, FAQs and history from your old bot
- Removes duplicates and outdated answers along the way
- Checks new answers against the old ones before launch
$2,500
10–20 working days
What it is
Data Migration from Existing Bot is an add-on that moves flows, FAQs and history from your current bot or tool into an Upmark Labs conversational agent. Content is exported, cleaned, mapped to the new agent and checked. It is bought with a voice, messaging, chatbot or action agent.
Why businesses buy it
The work inside an old bot represents years of customer questions and fixes. Starting from scratch throws that away, and staff rarely remember everything that was in there. A careful migration keeps what works, drops what is out of date and gives your new agent a strong start. The written scope covers export from one existing tool, a cleaning pass, mapping to the new agent and a comparison of old and new answers on sample questions, so nothing important is lost in the switch.
Problems this solves
Years of bot flows and FAQs feel too costly to rebuild
This add-on moves flows, FAQs and history from your current bot or tool into the new Upmark Labs agent. Your past work carries over rather than starting again from a blank page.
Old content is messy, duplicated or out of date
Content is exported, cleaned and mapped to the new agent before it goes in. Duplicates and broken pieces are dealt with during the move, not carried across unchanged.
Switching tools risks losing answers customers rely on
Migrated content is checked in the new agent and tested with it before launch. The test report shows what moved across, so gaps are visible before customers meet them.
A good fit if
You are replacing a chatbot or voice bot that already holds years of FAQs and tuned flows.
Your team does not want to retype answers that already exist somewhere.
Past conversations matter to you, for reporting or for context on returning customers.
The new agent is an Upmark Labs voice, messaging, chatbot or action agent.
Not the right fit if
Your extra content lives in documents or help pages, not in a bot. Knowledge Base Expansion adds those sources.
Your data sits in spreadsheets you want loaded regularly. CSV Import Pipeline sets up that route.
Your new product is not conversational, such as a workflow automation or a report. This add-on only fits agents.
Your current tool has no way to export its content. Ask for a Change Quote; migration then depends on what can be read.
How it works
- The old bot is inventoried. We list its flows, FAQs and stored history, and what its export or API can provide.
- Content is exported and cleaned. Duplicates, outdated answers and broken flows are flagged for you to keep, fix or drop.
- Everything is mapped. Old flows become flows in the new agent, FAQs become approved knowledge, and history is stored where the agent can use it.
- The migration is checked. Sample questions the old bot handled are asked of the new agent to compare the answers.
- You review what moved with one revision round, then get a migration report and a written walkthrough.
What you provide within 72 hours
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
- The order reference of the new agent
- Admin or export access to your current bot or tool, shared securely as agreed at intake
- Which flows and FAQs are still in use, and which can be dropped
- How much conversation history you want moved, and any history that must stay behind
- One person who signs off the cleaned content
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.
Timeline
Start
Old bot access and export options confirmed
Week 1
Flows, FAQs and history exported
Week 2
Content cleaned, decisions sent to you
Week 2
Content mapped into the new agent and checked
Week 2
Your review and one revision round
Go-live
Migration complete, report and walkthrough handed over
| Option | Delivery time | Price |
|---|---|---|
| Standard | 10–20 working days | $2,500 |
What you receive at handover
- Flows, FAQs and history from your current bot or tool migrated into the new agent
- Cleaned and mapped content checked inside the new agent
- Updated documentation describing what was moved
- A test report, a handoff note and a short written walkthrough
Expected benefits and how to measure them
- Can shorten the switch from your old bot to the new agent
- Helps keep answers customers already rely on
- Gives you a cleaner starting set of content
- Content carried over
- Compare the list of flows and FAQs in the old tool with what is live in the new agent.
- Unanswered questions after switch
- Count unanswered conversations in the first month on the new agent and compare with the old bot's last month.
- Customer complaints during the switch
- Track complaints about the bot for the month before and after the change.
Before you start: Export a list of the flows and FAQs in your current bot. Note its recent unanswered-question count if it reports one.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
Migration is a one-time job. Afterwards, the new agent's running costs are the same as without it, billed to your own accounts. Keep the old tool's subscription active until the migration is signed off.
Ask about running costsCustom requirements
Migrating from more than one old tool, or keeping the old and new bots running in sync, is beyond this add-on. Add a checkout note and you get a written Change Quote. Larger or bespoke projects go through the Custom AI request form instead.
Request a custom versionKeep it running
After migration, migrated FAQs are maintained like any other knowledge under the parent product's maintenance, which grows in line with the add-on's price.
Adds $125/mo to maintenance
Covered by the main product's maintenance, which grows by this amount.
How maintenance worksHow this compares
| Do it yourself with a SaaS tool | Hire a custom agency | Upmark Labs | |
|---|---|---|---|
| Price | A new vendor may offer an import tool for its own format only | An agency quotes migration after an audit | Ours is one fixed price, shown before you buy |
| Cleaning | Content is copied as it is | Depends on the brief | Ours flags duplicates and outdated answers before they move |
| Checking | Left to you | Set per project | Ours compares old and new answers on sample questions |
Questions about this product
Which bots can you migrate from?
Any bot or tool that can export its content or exposes it through an API. Most chatbot builders, helpdesk bots and voice platforms allow at least an export of FAQs and flows. We confirm what your tool offers on day one. If nothing can be exported, migration is quoted separately.
Will my old flows work the same in the new agent?
They are rebuilt to do the same job, not copied line for line. Old bots often use rigid button paths; the new agent may handle the same request in fewer steps. We check sample questions against both so you can see the outcome matches what the old flow achieved.
Do you move every past conversation?
We move the history you choose, within what the old tool can export. Some teams keep a year, others only open cases. History you want left behind stays behind. We agree the scope at intake, including any history that must not be copied for privacy reasons.
Should I clean up my FAQs before migrating?
No, that is part of the job. During cleaning we flag duplicates, contradictions and answers that look outdated, and send you a list of decisions. You choose what to keep, fix or drop, and only the approved content moves into the new agent.
Can the migration happen in the same order as the new agent?
Yes, and that is the smoothest route, because the new agent is built with the migrated content from the start. The migration follows the agent's delivery speed, and faster speeds are available, each with a fixed price and date shown before you pay. Give us export access to the old tool during intake.
When can I switch off the old bot?
After you sign off the migration report and the new agent is live. Until then, keep the old tool running and its subscription active, because we read from it during the export and the checks. Most teams switch off once the new agent has handled real traffic for a short while.
Bring your old bot's knowledge with you.
Add Data Migration from Existing Bot and your flows, FAQs and chosen history are exported, cleaned and moved into the new agent, then checked against the old answers.
Works well with
WhatsApp Agents
WhatsApp AI Support Agent
Resolves customer questions on WhatsApp with human handoff.
Front Line
AI Customer Support Agent
Resolves customer questions across chat and email using your knowledge base and hands off complex cases.