# Lexful

> Lexful helps MSPs turn operational context into client-ready documentation, workflows, and insight.

A complete index of Lexful's public product, use-case, integration, resource, company, legal, and editorial content.

For a shorter product-first guide, see [llms.txt](https://lexful.ai/llms.txt).

## Platform

Product layers and platform overview.

- [Product](https://lexful.ai/product): Lexful gives your team and your AI tools a structured, queryable knowledge layer — covering assets, credentials, playbooks, and client context. Built for MSPs.
  - The MSP documentation platform built for the AI era: Six layers, one knowledge OS. Lexful does everything a documentation tool does (asset, document, and password management), and where legacy tools end is where we start.
  - One connected knowledge graph. Six layers working it: Every asset, credential, document, and relationship lives in one structured knowledge layer that your team and your AI tools share.
  - Ask Lex: AI as UI: Find, create, update, check, summarize. Ask in plain English; get the answer for the right client in under 30 seconds, with sources and reasoning shown. It follows connections, not keywords, so the answer comes back right for the right client.
  - Document Engine: Raw notes become structured SOPs. In-document AI actions, templates, review dates. And Skills: save any prompt as a reusable Skill, private or shared, and run it again with a slash command.
  - Asset Intelligence: Full-context device and configuration records, related items, custom asset types, version history on everything. Organized by the Tag Framework: tags, not folders, with Expirations flagging certs, domains, and warranties before they lapse.
  - Agent Access (MCP): A secure MCP connection lets Claude, Copilot, Cursor, or your RMM automation query Lexful directly, permissions enforced end-to-end. Plus a full REST API and webhooks.
  - Documentation that keeps itself current: Three forces, working together.
  - Live sync from PSA and RMM: Records reflect reality, not someone’s memory.
  - Lex Skills catch drift: They flag stale information and bring formatting into house style in one pass.
- [Agent Access](https://lexful.ai/product/agent-access): Connect governed Lexful knowledge to the agents and automations your MSP already uses.
- [Ask Lex](https://lexful.ai/product/ask-lex): Ask any question about any client and get a grounded answer from your own governed knowledge.
- [Asset Intelligence](https://lexful.ai/product/assets): Keep every asset, configuration, credential, and relationship structured, connected, and queryable.
- [Credential Vault](https://lexful.ai/product/credentials): Keep credentials in the operational context where technicians need them, with permissions, auditability, and OTP support.
- [Document Engine](https://lexful.ai/product/documentation): Turn raw notes and connected PSA/RMM data into living SOPs your team can trust.
- [Expirations](https://lexful.ai/product/expirations): Certificates, domains, warranties, licenses, and review dates flagged before they lapse.
- [Governance & RBAC](https://lexful.ai/product/governance): Apply roles, groups, grants, and deny scopes across people, Ask Lex, and every connected agent.
- [Skills](https://lexful.ai/product/skills): Save any prompt as a Skill and run it again with a slash command. Private or shared with the team.
- [Tags](https://lexful.ai/product/tags): Folder trees break at MSP scale and starve AI. Tags organize every record for humans and machines.

## Why Lexful

The case for an AI-native, governed knowledge platform for MSPs.

- [Why](https://lexful.ai/why): MSPs don't have a tool problem — they have a knowledge problem. Lexful fixes it: structured context your team and agents can actually act on.
- [Relentless Innovation](https://lexful.ai/why/innovation): Lexful is MSP-first, API-first, and MCP-first—built to help MSPs move through the AI-native shift.
- [Legacy Tools vs Lexful](https://lexful.ai/why/legacy-tools): Legacy IT documentation stores records. Lexful makes them usable by techs and AI agents.
- [Migration without Mayhem](https://lexful.ai/why/migration): Move documentation, passwords, attachments, and relationships to Lexful without a disruptive cutover.

## Use cases

Operational outcomes across the MSP service lifecycle.

- [Solutions](https://lexful.ai/solutions): Run the desk and business with connected, governed operational knowledge.
- [Client Self-Service](https://lexful.ai/solutions/client-self-service): A sourced, permission-scoped AI help center for your clients' own environment.
- [Compliance](https://lexful.ai/solutions/compliance): Save compliance checks as Skills and run them against live documentation with human approval.
- [Create Documentation](https://lexful.ai/solutions/create-documentation): Runbooks, SOPs, and client guides drafted from connected records, then tech-approved.
- [Onboard Clients](https://lexful.ai/solutions/onboard-clients): Bring in a new client stack, structure the records, and identify the gaps on day one.
- [Onboard Technicians](https://lexful.ai/solutions/onboard-technicians): Give new MSP technicians sourced answers from day one.
- [QBR Prep](https://lexful.ai/solutions/qbr-prep): Ask Lex assembles the client's network, asset, warranty, and documentation picture from live records.
- [Resolve Tickets Faster](https://lexful.ai/solutions/resolve-tickets): Ask Lex gives technicians a sourced answer for the right client in seconds.

## Pricing, trust, and getting started

Pricing, trust posture, and evaluation paths.

- [Demo](https://lexful.ai/demo): See Lexful in action. Book a personalized 30-minute demo and learn how Lexful turns tribal knowledge into machine intelligence for your MSP.
  - Documentation for the AI Era: Most MSPs lose 15–20 minutes per ticket digging for context. We'll show you what under 30 seconds looks like — on your real workflows, with your real questions.
- [Pricing](https://lexful.ai/pricing): One plan. No feature tiers. No surprise add-ons. $20 per active client per month — everything included.
  - Simple. All in: One plan. No feature tiers. No surprise add-ons.
  - Standard: Billed per licensed client — one where your team manages assets, runs AI workflows, and creates documentation. Read-only clients are always free. Includes Unlimited internal users; Unlimited documents, assets & passwords; Ask Lex — AI search & actions across all client data
  - Get started on one AI-native platform that scales with you: Month one is free, the plan stays simple, and you license only the clients you actively manage. Keep unlicensed clients in Lexful, read-only, for reference.
  - Month one is on us: Start with the full platform and your whole team. Cancel anytime.
  - One simple annual plan: After the first month, a 12-month term is billed monthly at $20 per licensed client, with a $300 monthly minimum.
  - License what you manage: Licensed clients get the full platform. Unlicensed clients stay free, read-only, searchable, and kept current by integrations.
- [Trial](https://lexful.ai/trial): Get started with Lexful and see how AI-powered knowledge operations can help your MSP find answers faster.
  - Try Lexful with your own MSP knowledge: Spin up a guided workspace and see how Lexful turns scattered documents, stale notes, and tribal knowledge into answers your team can actually use.
- [Trust Center](https://lexful.ai/trust): Review Lexful's security posture, compliance certifications, and governance policies. Request access to our SOC 2 Type II report, security policies, and more.
  - Welcome: Security and Governance Built Into the Platform
  - Security by Design: Lexful is designed to protect MSP knowledge, enforce access controls, and support compliance without compromising usability. Security is not layered on top of the platform — it is embedded in how documentation, credentials, permissions, and AI access are structured and governed. Customer data is protected through role-based access control, tenant-level isolation, encryption in transit (TLS), and encryption at rest. Access to documentation, credentials, and AI-generated responses is always permission-aware and enforced at the platform level.
  - Certifications & Standards
  - Type II: SOC 2
  - In progress: ISO 27001
  - Uptime SLA: 99.9%
- [Contact](https://lexful.ai/contact): Get in touch with the Lexful team. Whether you're an MSP exploring the platform, a potential partner, or press — we'd love to connect.

## Integrations

Integration index and public integration detail pages.

- [Integrations](https://lexful.ai/integrations): Explore Lexful Docs integrations for PSA and RMM tools.
- [Autotask PSA Integration](https://lexful.ai/integrations/autotask-psa): Lexful connects Autotask PSA context to your documentation layer so teams can answer questions with the right client, asset, and service background.
- [ConnectWise PSA Integration](https://lexful.ai/integrations/connectwise-psa): Lexful uses ConnectWise PSA context to ground documentation and answers in the companies, contacts, assets, and service records your team already trusts.
- [ConnectWise RMM Integration](https://lexful.ai/integrations/connectwise-rmm): Lexful uses ConnectWise RMM context to connect device and environment details with the documentation technicians use to resolve issues.
- [Datto RMM Integration](https://lexful.ai/integrations/datto-rmm): The planned Datto RMM integration will bring endpoint and environment context into Lexful Docs so technicians can answer support questions with fewer manual lookups.
- [HaloPSA Integration](https://lexful.ai/integrations/halopsa): Lexful brings HaloPSA service context into the knowledge layer so teams can pair documentation with live client details.
- [Liongard Integration](https://lexful.ai/integrations/liongard): Lexful can use Liongard environment context to help teams analyze client systems and operational change over time.
- [N-able N-central Integration](https://lexful.ai/integrations/n-able-n-central): Lexful Analytics can bring N-able N-central context into MSP reporting so operational health and device data are easier to analyze with client and service context.
- [Neo Agent Integration](https://lexful.ai/integrations/neo-agent): Connect Neo Agent with Lexful Docs to bring client policies and asset context into AI-powered ticket resolution and service desk automation.
- [NinjaOne RMM Integration](https://lexful.ai/integrations/ninjaone-rmm): Lexful connects NinjaOne environment context to your documentation so teams can answer operational questions with current endpoint and device insight.
- [ScalePad Integration](https://lexful.ai/integrations/scalepad): The ScalePad integration helps Lexful Docs keep customer success context close to the documentation your team uses to answer client and account questions.

## Resources

Resource index, downloadable assets, templates, and public resource detail pages.

- [Resources](https://lexful.ai/resources): Field-tested guides, templates, and tools for MSPs navigating delivery, strategy, risk, and growth. Practical resources you can use immediately with your team.
- [The Lex Prompt Playbook](https://lexful.ai/resources/lex-prompt-playbook): The prompts MSP partners run most in Lex, plus the patterns that turn a vague answer into one a technician can act on.
- [Lexful Technical FAQ](https://lexful.ai/resources/technical-faq): Technical answers on Lexful security, AI grounding, integrations, migration, and data ownership.

## Editorial

Blog, news, updates, events, case studies, guides, and related public editorial routes.

- [Blog](https://lexful.ai/blog): Practical insights on agentic AI, knowledge operations, and building a modern MSP — from the team at Lexful.
- [News](https://lexful.ai/news): Official press releases, funding announcements, and media coverage from Lexful — as we redefine how MSPs manage knowledge and context.
- [Lexful Announces General Availability of AI-Native Documentation Platform Built for the AI Era](https://lexful.ai/news/general-availability-press-release): Lexful today announced general availability of its AI-native IT documentation platform for MSPs, delivering migration without mayhem through expanded integrations and AI-native knowledge operations.
- [Agentic AI for MSPs: What to Automate and What to Keep Human](https://lexful.ai/blog/agentic-ai-for-msps): A control-first blueprint for adopting agentic AI in managed services without introducing operational risk.
- [How AI Architecture Becomes an MSP Advantage](https://lexful.ai/blog/ai-architecture-advantage): A practical lens on architecture decisions that compound into better margin, faster execution, and stronger trust.
- [What AI Reveals About Broken MSP Team Boundaries](https://lexful.ai/blog/ai-broken-team-boundaries): AI exposes unclear MSP team boundaries through missed handoffs, wrong escalations, and confidently incorrect resolutions.
- [How AI Exposes Asset Sprawl MSPs Have Been Ignoring for Years](https://lexful.ai/blog/ai-exposes-asset-sprawl): AI exposes the gap between what MSPs think they manage and what they actually manage. Asset sprawl becomes visible fast.
- [Why AI Isn't Working for MSPs Yet](https://lexful.ai/blog/ai-gap-for-msps): Why most MSP AI deployments fall short, and how AI can fit real MSP workflows well enough to feel like relief instead of disruption.
- [AI hallucination and the state of IT documentation](https://lexful.ai/blog/ai-hallucination-and-it-documentation): Why AI assistants hallucinate on IT documentation, the mechanics that stop it (a closed corpus, cited sources, permissions before generation), and why the fix lives in the data layer.
- [AI-Native Architecture for MSP Platforms](https://lexful.ai/blog/ai-native-architecture): The architectural foundations that make AI reliable in MSP operations: structured context, APIs, and governed execution boundaries.
- [How to Build an AI-Ready Knowledge Base That Actually Works](https://lexful.ai/blog/ai-ready-knowledge-base): AI-ready knowledge bases need structure, source visibility, and workflows that help models produce reliable MSP answers.
- [How AI Will Reshape MSP Business Models](https://lexful.ai/blog/ai-reshaping-msp-business): AI is changing how MSPs price, package, and specialize services. Here's what becomes more valuable as delivery models shift.
- [What AI Actually Needs to Resolve Tickets End-to-End](https://lexful.ai/blog/ai-resolve-tickets-end-to-end): Ticket resolution is a system, not a single parsing step. Production AI needs context, permissions, actions, and feedback loops.
- [The Problem With Automating Tier-1 Without Fixing Context](https://lexful.ai/blog/automating-tier1-context): Automating Tier-1 without fixing context does not reduce MSP workload. It relocates the problem to higher-cost teams.
- [AI-Native Architecture: Building Lexful Different from Day One](https://lexful.ai/blog/building-lexful-ai-first): How Lexful's AI-native, API-first, zero-trust architecture makes MSP knowledge structured, secure, and ready for agentic workflows.
- [Client Trust in the AI Era: What MSP Buyers Must Operationalize](https://lexful.ai/blog/client-trust-ai): Policies, communication standards, and governance controls MSPs need to keep client trust while scaling AI-enabled operations.
- [Culture > Code: Why the Most Forward MSPs Don't Start with AI at All](https://lexful.ai/blog/culture-code-msp-ai): AI projects in MSPs usually fail from lack of belief, not lack of effort. Why culture decides whether AI adoption sticks.
- ["We Were Done an Hour Ago": How an AI-First MSP Rebuilt Its Documentation on Lexful](https://lexful.ai/blog/descent-it-rebuilt-documentation-on-lexful): An AI-first MSP cut documentation time from hours to minutes with Lexful. Steven Saehrig on the one-day migration, AI-generated docs, and happier co-managed clients.
- [From Documentation to Decision Systems: Rethinking MSP Knowledge Bases](https://lexful.ai/blog/documentation-to-decision-systems): MSPs need more than passive documentation. Decision systems surface the right operational knowledge at the right moment.
- [Enterprise-Grade Security: Built for Trust from Day One](https://lexful.ai/blog/enterprise-grade-security-msp): Security shapes every Lexful architecture decision, from data modeling to API authorization. Trust is built in, not added later.
- [Your Fastest Technician is Hiding Your Documentation Problem](https://lexful.ai/blog/fastest-tech-hiding-documentation-problem): Two-click speed in MSP documentation is memorized routes covering for broken search. Here are the hidden costs, and what changes when retrieval replaces routes.
- [The Hidden Cost of Human-Centered Credential Workflows](https://lexful.ai/blog/hidden-cost-credential-workflows): Credential workflows are operational infrastructure. Human-centered processes create hidden MSP costs that compound over time.
- [The Hidden Cost of Storage-Based MSP Documentation Tools](https://lexful.ai/blog/hidden-cost-of-storage): Legacy MSP documentation tools store what you type and produce nothing. Here's the hidden labor cost of manual documentation, and what changes when the platform does the work.
- [The Hidden Power in Every MSP's Inbox: A Practical Guide to Building Your Own Internal GPT](https://lexful.ai/blog/hidden-power-msp-inbox): Every MSP inbox holds client requests, vendor responses, and operational knowledge. Here is how to turn that context into an internal GPT.
- [Human-in-the-Loop (HITL): Balancing Automation With Human Expertise in MSP Operations](https://lexful.ai/blog/human-in-the-loop-msp): The modern MSPs don't choose between humans and AI — they design for both. Here's where automation adds value and where human oversight remains non-negotiable.
- [The Hidden Risk Behind Admin Access in MSPs](https://lexful.ai/blog/msp-admin-access-risk): Admin access concentrates MSP risk. Every elevated account, credential, and memory-driven workflow can become a liability.
- [MSP Agentic AI: The Future of Managed Services Operations](https://lexful.ai/blog/msp-agentic-ai-operations): MSPs are entering the agentic AI era, where systems reason, adapt, and act across managed services operations.
- [The Cost Curve Shift AI Introduces (and Why Many MSPs Miss It)](https://lexful.ai/blog/msp-ai-cost-curve): AI does not just reduce MSP costs; it restructures them. Why the cost curve changes when knowledge and workflows become active.
- [Why MSP AI Adoption Is a Culture Problem Before a Tool Problem](https://lexful.ai/blog/msp-ai-culture): The organizational behaviors that separate MSPs with sustainable AI outcomes from those stuck in pilot mode.
- [AI Governance for MSPs: Policies, Security, and Compliance from Day One](https://lexful.ai/blog/msp-ai-governance): Building trust and accountability before AI touches your workflows. AI is transforming MSP operations — but there's a hidden risk few MSPs address upfront: governance.
- [The 6 Hidden Workflows Inside Every MSP That AI Can Automate First](https://lexful.ai/blog/msp-ai-hidden-workflows): A practical guide to finding AI ROI in month one by starting with the hidden workflows MSP teams touch hundreds of times a week.
- [The Lifecycle of AI in MSPs: From Pilot to Full-Scale Deployment](https://lexful.ai/blog/msp-ai-lifecycle-pilot): How MSPs can scale AI safely and effectively — a practical guide through the five phases from exploration to continuous improvement.
- [The ROI Illusion in MSP AI: Why Most Projects Fail Before They Start](https://lexful.ai/blog/msp-ai-roi-illusion): Most MSPs think AI automatically creates value. Here's why it doesn't — and the foundational problems you must solve before ROI is even possible.
- [MSP AI Security: The Architecture That Keeps Trust Intact](https://lexful.ai/blog/msp-ai-security): Security-by-design practices for MSP AI systems, from zero-trust access to auditable operational controls.
- [From Noise to Signals: How MSPs Can Use AI to Cut 70% of Ticket Fatigue](https://lexful.ai/blog/msp-ai-ticket-fatigue): AI-assisted triage can reduce redundant MSP tickets by connecting alerts, root causes, and client context before fatigue takes over.
- [6 AI Workflows MSPs Should Automate First](https://lexful.ai/blog/msp-ai-workflows): The fastest path to measurable AI ROI for MSPs: automate repetitive workflows that drain technician capacity and margin.
- [Data Debt in MSPs: Why Garbage In Still Means Garbage Out](https://lexful.ai/blog/msp-data-debt): AI is only as smart as the data it sees. Why inconsistent records, unstructured notes, and siloed systems quietly kill MSP AI initiatives.
- [The Lifecycle View MSPs Need Before They Add Automation](https://lexful.ai/blog/msp-lifecycle-before-automation): Why MSP automation fails when teams optimize steps instead of systems, and what lifecycle thinking changes before AI enters.
- [The Offboarding Nightmare: Where MSPs Leak Risk and Knowledge](https://lexful.ai/blog/msp-offboarding-risk): Offboarding combines access revocation, knowledge transfer, and compliance closure, making it one of the riskiest MSP workflows.
- [What the Latest Microsoft Outage Reveals About MSP Outage Readiness](https://lexful.ai/blog/msp-outage-readiness): Major outages reveal operational fragility. MSPs struggle when processes are undocumented and knowledge is trapped in people.
- [Predictive Maintenance for MSPs: Where It Delivers Real Value](https://lexful.ai/blog/msp-predictive-maintenance): How MSPs separate predictive maintenance hype from practical gains using data quality, process design, and human validation.
- [Why MSPs Can't Automate What They Can't Inventory](https://lexful.ai/blog/msps-cant-automate-inventory): MSPs cannot automate what they cannot inventory. Incomplete asset truth makes every workflow built on top of it weaker.
- [How MSPs Lose Knowledge Every Time a Ticket Is Closed](https://lexful.ai/blog/msps-lose-knowledge-tickets): Every resolved ticket contains institutional intelligence. Most MSPs lose that knowledge instead of turning it into reusable context.
- [Why MSPs Are Outgrowing Documentation Tools (And What Comes Next)](https://lexful.ai/blog/msps-outgrowing-documentation-tools-knowledgeops): MSPs have outgrown documentation tools. KnowledgeOps makes MSP knowledge structured, current, and usable by humans and AI.
- [Why MSPs Struggle to Explain Their Own Operations](https://lexful.ai/blog/msps-struggle-explain-operations): Most MSPs know what services they offer, but not how work actually flows. That operating model gap becomes critical with AI.
- [Why Prompt Engineering Is a Dead End for MSPs](https://lexful.ai/blog/prompt-engineering-dead-end): Prompt engineering can improve outputs, but MSPs building production AI workflows need architecture, not just better prompts.
- [How MSPs Reduce Ticket Noise Without Replacing Their Stack](https://lexful.ai/blog/reduce-ticket-noise): A practical framework for cutting alert and ticket noise so technicians can focus on customer-impacting work.
- [Search is Broken: Why Tribal Knowledge Still Exists in MSPs](https://lexful.ai/blog/search-is-broken-why-tribal-knowledge-still-exists-in-msps): Why search broke in MSP documentation, why bolted-on AI does not fix it, and what better search architecture requires.
- [The Difference Between "Searchable" and "Actionable" Knowledge for AI](https://lexful.ai/blog/searchable-vs-actionable-knowledge): Most MSPs have searchable knowledge. Very few have actionable knowledge. The difference determines whether your AI delivers reliable answers or confident hallucinations.
- [The Silent Risks of Shadow IT in MSP-Managed Environments](https://lexful.ai/blog/shadow-it-risk-msp): Shadow IT quietly accumulates risk in managed environments. What MSPs cannot see, document, or govern becomes fragile fast.
- [You Can't Solve MSP Tribal Knowledge Without AI](https://lexful.ai/blog/solve-msp-tribal-knowledge-without-ai): MSPs have understood the tribal knowledge problem for a decade. Here's why legacy documentation never fixed it, and what changes when capture becomes a byproduct of the work.
- [Why Tier-2 and Tier-3 Work Break First When MSPs Add Automation](https://lexful.ai/blog/tier2-tier3-break-automation): Automation often starts at Tier-1, but Tier-2 and Tier-3 engineers feel the pressure first when MSP context is missing.
- ["Customer Zero": How TransformITive Made Lexful Its Knowledge Layer](https://lexful.ai/blog/transformitive-made-lexful-its-knowledge-layer): An AI-first MSP rebuilt its stack around Lexful. From a fifteen-second statement of work to a one-hour IT Glue migration, the CEO and Director of Client Services share what changed.
- [What Great MSP Documentation Actually Looks Like](https://lexful.ai/blog/what-great-msp-documentation-actually-looks-like): The six properties that separate great MSP documentation from a large pile of records, and the series that takes each one apart.
- [When SOPs Break at Scale and What MSPs Should Build Next](https://lexful.ai/blog/when-sops-break): Why static SOP libraries become bottlenecks in complex MSP environments and how to replace them with governed knowledge operations.
- [Why MSP Documentation Goes Stale the Moment It's Written](https://lexful.ai/blog/why-msp-documentation-goes-stale): Why MSP documentation goes stale, why audits and homemade AI layers can't keep up, and what an engineered approach to freshness actually looks like.
- [AI-Native IT Documentation Platform Redefines How MSPs Work, Solving Pain Points and Generating Value in Real Time](https://lexful.ai/news/launch-press-release): Today at Right of Boom, Lexful introduced its AI-native, secure IT documentation platform built exclusively for MSPs to modernize operations.

## Company

Company and recruiting pages.

- [About](https://lexful.ai/about): Meet the MSP operators, SaaS founders, and AI architects building Lexful — the knowledge operating system that turns tribal knowledge into machine intelligence.
- [Careers](https://lexful.ai/careers): Join a remote-first team building the knowledge OS for managed service providers. Equity-backed, high-impact, and doing work that actually matters.

## Legal

Privacy, terms, and legal pages.

- [Privacy Policy](https://lexful.ai/privacy): Learn how Lexful collects, uses, and protects your personal information. Your privacy matters — here's exactly what we do with your data.
- [Terms of Use](https://lexful.ai/terms): Lexful Website Terms of Use. Please read these terms carefully before accessing or using our platform and services.

## Frequently asked questions

### What can clients see?
Only the records their client-scoped permissions allow.

Source: Client Self-Service
### Does this replace the MSP relationship?
No. It deflects routine context questions so your team can handle the work that needs them.

Source: Client Self-Service
### Can we use our own framework?
Yes. Skills can use your NIST, CMMC, QBR, or internal quality framework.

Source: Compliance
### Can a Skill change production documentation?
No. It proposes changes and waits for human approval.

Source: Compliance
### Does generated documentation match our standards?
Attach your template and Lex conforms to it; standardize formatting on anything imported.

Source: Create Documentation
### Do we lose control to the AI?
No. Lex drafts and proposes; a human approves before anything lands.

Source: Create Documentation
### Can Lexful help with a new client migration?
Yes. Sync the stack, structure the handed-over documentation, and identify undocumented items.

Source: Onboard Clients
### What happens to existing documentation?
Lex maps it into connected records instead of forcing a blank-slate rewrite.

Source: Onboard Clients
### How long does onboarding take with Lexful?
Teams reach useful independence in days once new techs can query the environment instead of memorizing it.

Source: Onboard Technicians
### What happens when a senior engineer leaves?
Their knowledge stays captured in the flow of work and queryable by whoever is next.

Source: Onboard Technicians
### Does this replace ScalePad?
No. Lexful arms the person preparing the review with the current environment picture.

Source: QBR Prep
### Where does the data come from?
Your connected PSA, RMM, and documentation, with sources shown.

Source: QBR Prep
### How much time do techs lose per ticket?
Across the desk, 15 to 20 minutes hunting for context is typical. Ask Lex collapses that to a single sourced answer.

Source: Resolve Tickets Faster
### Does it work for junior techs?
A first-week tech gets the same permission-scoped answer your best engineer would give.

Source: Resolve Tickets Faster
### 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.

Source: Migration without Mayhem
### 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.

Source: Migration without Mayhem
### 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.

Source: Migration without Mayhem
### 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.

Source: Migration without Mayhem
### 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.

Source: Migration without Mayhem
### 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.

Source: Migration without Mayhem