MIGRATION WITHOUT MAYHEM
Leave your legacy tool behind. Keep everything it holds.
Bring your documentation, passwords, attachments, and the relationships between them into Lexful. Keep your current tool running in parallel until your team is ready.
ON YOUR TERMS
A migration should be reversible, reviewable, and non-disruptive.
The importer reads your source data, supports retries and resume, and can be run again while your team continues working in the current system. Review the result before choosing a cutover date.
THE REAL RISK
What usually goes wrong in documentation migrations?
Legacy documentation is a relational database wearing a wiki costume. Companies link to contacts, configurations to passwords, assets to everything. Export it to a flat CSV and those links vanish. Your techs land in a new tool where nothing connects to anything.
WHAT TRANSFERS
Everything that matters, with its context intact.
Transfer manifest · Nothing arrives orphaned
REC.01
Organizations, contacts, configurations, and assets
✓ Mapped into Lexful’s connected model, custom asset types included
DOC.02
Documents with their formatting
✓ Headings, tables, and checklists survive intact
ATT.03
Attachments and inline images
✓ Rack photos, vendor PDFs, and screenshots stay with their records; you choose what transfers
PWD.04
Encrypted passwords and OTP seeds
✓ Your MFA codes keep working on day one
REL.05
The relationships between it all
✓ Rebuilt in the knowledge graph, not imported as flat files
HOW IT WORKS
Four steps. One afternoon.
Sign in once
A desktop importer app. Credentials are stored with the operating system’s built-in encryption; nothing sensitive in plain text.
Choose what comes
Exclude specific organizations or archived data. Bring your whole book or start with a subset.
Let it run
Retries, resume support, and automatic recovery after network issues or reboots. Read-only against your source and non-destructive; safe to re-run anytime.
Run in parallel
Keep your legacy tool live while your team verifies answers in Lexful. Cut over when you’re confident, not when a deadline says so.
What got you here won't get you there.
Start the review now, then choose the migration pace that fits your team.
QUESTIONS
Migration questions
Straight answers on timing, safety, what transfers, and support.
How long does migration take?
Most migrations run in an afternoon. Typical importer runtime is 30 minutes to 4 hours depending on the size of your book, and the guided desktop importer does the work.
Does my current tool keep running?
Yes. The importer is read-only against your source and non-destructive, so your legacy tool stays live and untouched. Run both in parallel and cut over when your team trusts the answers, not when a deadline says so.
What transfers into Lexful?
Organizations, contacts, configurations, and assets, including custom types; documents with their formatting; attachments and inline images; and encrypted passwords including OTP seeds, so MFA codes keep working on day one.
Do the relationships between records survive?
Yes. The importer rebuilds every link in the Lexful knowledge graph rather than dumping flat files, so password-to-config, config-to-company, and doc-to-asset connections arrive intact. That is what Ask Lex reads to answer correctly.
Which tools can we migrate from?
The IT documentation platforms MSPs use today. If you can export it, the guided importer can bring it in, and our team will confirm your exact source on a walkthrough.
What if the import is interrupted?
It recovers on its own. The importer retries, resumes, and auto-recovers after network drops or reboots, and it is always safe to re-run.
Does migration cost extra?
No. Migration support is included, and month one is free under the Proof of Value Guarantee. Bring your whole book in before you pay a dollar.