Laserfiche to SharePoint migration services
Laserfiche is a records-management platform, so the documents are the easy part. The template metadata, the retention schedules, the folder structure and the Laserfiche Workflow routing are what actually run the department. Our fixed-fee Laserfiche to SharePoint migration services map templates to content types, rebuild retention in Microsoft Purview, recreate workflows in Power Automate and preserve version history in SharePoint Online — delivered by senior US-based Microsoft engineers, one written price, typical delivery in 2–4 weeks, 30 days of hypercare included. And if integration is the better answer for your estate, we will tell you before you sign anything.
Representative dashboard — sample data
What you get
A file-sync tool holds files in folders. Laserfiche holds records with typed fields, schedules and routing wrapped around them. Moving the files without those three is how a department loses its filing system on cutover day.
Every Laserfiche template and its fields are inventoried with their types and list values, then rebuilt as SharePoint content types and site columns. The metadata travels with each document, so search and filtering work the way the records staff expect.
Records series, cutoff triggers and disposition rules are written down in your policy language, confirmed with the records officer, then rebuilt as Microsoft Purview retention labels and policies and tested on real documents before content moves.
Routing, approvals, notifications and field-setting rules that Laserfiche Workflow runs today are read definition by definition and rebuilt as flows against the destination library, with triggers and approvers documented for whoever inherits them.
Document versions are exported in order so SharePoint records the same chain with original dates and authors. Annotations, stamps and redactions are captured as a burned-in rendition next to the clean original, so nothing legally visible disappears.
A Laserfiche folder tree is usually a decade of departmental habit. It is mapped to sites and libraries around who owns the records and who needs to read them, with metadata doing the work that nested folders used to do.
Laserfiche ships its own SharePoint Online integration, and for some estates that is the better answer. We put both options and their trade-offs in front of you during scoping instead of assuming the migration you searched for is the one you need.
How it works
A free consultation plus a read of your Laserfiche repository tells us which templates carry real metadata, which retention schedules apply to which records series, which workflows and forms still run, and how much version history and annotation exists. You get a written scope, a wave plan, one fixed price and a cutover date.
Sites, libraries, content types, columns, Purview retention labels and Power Automate flows are built to the agreed design. One complete records series moves end to end — documents, versions, metadata, retention, routing — and the records staff exercise it on live work before anything else is touched.
Remaining content moves department by department with counts and metadata spot-checks at each step and a final pass that copies only what changed. Staff get short guides, Laserfiche goes read-only for an agreed reference window, and 30 days of hypercare follows.
Laserfiche publishes a SharePoint Online integration, and a fair number of the organizations that land on this page are already running it: Laserfiche as the repository of record, SharePoint as the collaboration layer, documents surfaced across the seam. If that arrangement is working, keeping it is a legitimate choice, and we will say so in the consultation rather than sell you a project. Integration keeps the Laserfiche investment intact and avoids re-training the records staff. What it does not do is remove the second licence bill, the second permission model, the second search index or the second place a retention policy has to be maintained.
Migration earns its keep when the goal is consolidation: one platform under one set of Microsoft 365 licences, one retention engine in Microsoft Purview records management (opens in new tab), and one index that Microsoft 365 Copilot can reason over. That last point is the driver we hear most often in 2026. Copilot only sees content in Microsoft 365, so a repository of contracts, permits, minutes or member files sitting in Laserfiche is invisible to it. There is no retirement date pushing you; Laserfiche is a live, supported product. The decision is about where you want the system of record to live for the next decade, and the consultation is where both answers get written down with their costs.
Every other SharePoint migration we publish, from file server to SharePoint migration through Dropbox, Box, Egnyte and ShareFile, starts from files in folders with permissions attached. Laserfiche starts somewhere else. A document in Laserfiche is a record: it was filed under a template, its fields were filled in by a clerk or a capture profile, a retention schedule was attached by its folder or its series, and a workflow may have routed it through review before it was ever visible. Move the file and leave those three behind and you have a PDF in a library that nobody can find by contract number, that will never be disposed of on schedule, and that stopped going to the approver on the day of cutover.
So the inventory reads the repository as a records system. Templates and fields come first, because they decide the SharePoint information architecture. Retention schedules come second, because they decide what Purview has to look like before any record lands. Workflows and forms come third, because they decide what Power Automate and Power Apps have to be running on the first morning. Only then do folder counts and file sizes matter, and even those are read against the metadata: a folder tree that was built to stand in for missing fields usually collapses into a flat library with columns and views once the fields exist.
This is the working checklist we take into the inventory session. The right-hand column is the point: nearly every row needs a decision from the records owner before copying starts, and the retention rows need it earliest, because they gate the pilot.
| In Laserfiche | Where it lands in Microsoft 365 | Decided before the first pass |
|---|---|---|
| Templates and fields | SharePoint content types and site columns (opens in new tab), published from the content type hub where several sites share them | Which templates are in live use, which fields are consistently populated, and which list values are still valid |
| Dynamic fields and lookup tables | Choice columns, managed metadata term sets, or lookup columns to a reference list | Whether the source list is a stable vocabulary or a live table someone else maintains |
| Folder tree and volumes | Sites per department or function, document libraries per records series, views replacing deep folder nesting | Who owns each branch, which branches are archive, and which folders exist only to compensate for missing metadata |
| Records retention schedules and cutoff | Purview retention labels and policies (opens in new tab), event-based retention for cutoff triggers such as contract end or employee separation | What each schedule actually requires in policy language, and who signs off that the rebuild matches it |
| Document versions | SharePoint version history, written in order with original modified dates and authors | Which folders had versioning enabled and how many versions per document need to come across |
| Annotations, stamps and redactions | A burned-in rendition stored alongside the clean original, with a column recording which is which | Whether annotations are legally part of the record, decorative, or both depending on the series |
| Laserfiche Workflow | Power Automate flows triggered on item created or modified, with approvals recorded on the item | Which workflow definitions still fire, who approves, and which have been silently dead for a year |
| Laserfiche Forms | Power Apps forms on a SharePoint list, or Microsoft Forms for simple intake, feeding the same flows | Which forms are public-facing, which need attachments and signatures, and where submissions must file |
| Scanning and capture profiles | Scan-to-SharePoint from the multifunction device, with a flow applying metadata by folder or barcode | Which capture paths are still used, and whether OCR quality on old scans meets the search expectation |
| Security tags and access rights | SharePoint permission levels on Entra security groups at site or library level, with inheritance intact | Which entry access controls are real restrictions and which are historical accidents |
| Public portal and records requests | An external-facing SharePoint site, or a Power Pages portal where the public needs a branded front door | Whether public access is read-only browsing, a request intake, or both |
| Audit trail | The Purview audit log (opens in new tab) going forward, with the Laserfiche audit export retained as a read-only archive | How far back the records officer needs to answer access questions, and in what form |
On tooling: Microsoft's own migration utilities read file shares, SharePoint Server and a handful of cloud storage services, and Laserfiche is not among them. Content is therefore exported from the repository with its metadata and version chain, staged as a structured file set, and loaded into SharePoint with the metadata mapped column by column, using the SharePoint Migration Tool (opens in new tab) or the migration API for the load, and a purpose-built pass for the metadata and versions. Nothing in Laserfiche is deleted by any of this; the migration copies, which is why the repository can stay live through the waves and read-only afterwards.
The objection we hear from a city clerk, a credit union compliance manager or a district records officer is not technical. It is whether the schedule the organization is legally bound to still holds after the move. It is the right question, and the wrong answer is a reassuring shrug. Retention in Laserfiche is a schedule with cutoff instructions attached to a records series or a folder. Retention in Microsoft 365 is a Purview label or policy applied to a site, a library or a content type, with event-based retention for the triggers that do not run from a date. Those are different mechanisms, so the migration is the moment the schedule gets re-read rather than re-copied.
In practice that means each schedule is written down during inventory in the words your policy uses, with its trigger, its period and its disposition. The records officer confirms the list, often the first time it has been in one document. It is configured in Purview, applied to the pilot series, and proven against real documents before a second series moves. Where a series needs the stricter behaviour of a declared record, the label is configured that way, and the audit trail from that point forward is Purview's. Organizations that want the whole tenant configuration checked before Copilot gets anywhere near it usually read our guide to Copilot data governance and permissions clean-up at the same time, because a records migration is exactly the moment to fix oversharing rather than inherit it.
Laserfiche Workflow and Laserfiche Forms have no importer into the Power Platform, and any vendor who implies otherwise is describing a manual rebuild with a nicer word. What we do is read every workflow definition, list the ones that have actually fired in the last year with their trigger, routing, approvers and field-setting actions, and rebuild each of those as a Power Automate flow against the destination library so approvals are recorded on the item itself. Forms are rebuilt as Power Apps forms where they carry logic, attachments or signatures, and as Microsoft Forms where they are simple intake. The flows and forms are documented for the person who inherits them, which in a small records team is usually the person who built the originals a decade ago. Where the workflow estate is the larger part of the project, our Power Automate approval workflow consulting scopes that side in its own right.
Most Laserfiche exits sort into the same three phases. The table shows scope and typical timeline rather than prices, because an honest number requires reading your templates, your schedules and your workflow definitions first. You get one written price for the whole project instead of an hourly meter that rewards a slow migration, for the reasons set out in how our fixed-fee process works.
| Phase | Scope | Typical timeline | Fee |
|---|---|---|---|
| Phase 1 — Repository inventory and design | Templates, fields and list values catalogued; retention schedules written down and confirmed with the records officer; workflow and form definitions read and marked live or dead; version and annotation volumes measured; the integrate-versus-migrate decision documented; target site, library, content type and label design; a wave plan and cutover date | About 1 week | Fixed fee — scoped after your free consultation |
| Phase 2 — Pilot with one records series | Sites, libraries, content types, columns, Entra groups, Purview labels and policies and Power Automate flows built; one complete records series migrated end to end with versions, metadata, retention and routing, and exercised by the records staff on live work before anything else moves | About 1 week | Fixed fee — scoped after your free consultation |
| Phase 3 — Waves, validation, Laserfiche retirement | Remaining series migrated department by department with counts and metadata spot-checks at each step and a final delta pass at cutover; forms and capture paths switched; short guides for staff; Laserfiche set read-only for an agreed reference window; admin handover, then 30 days of included hypercare | 1–2 weeks, plus 30 days of hypercare | Fixed fee — scoped after your free consultation |
Everything lands in the tenant you own. The sites, content types, labels, policies, flows, forms, documentation and admin access are yours throughout, so your team can carry on in-house the moment hypercare ends.
The usual fit is an organization of roughly 20 to 500 people that adopted Laserfiche as its records system some years ago and now runs the rest of its work in Microsoft 365: a city or county department, a credit union, a school district, a utility, or a mid-size professional firm with a contracts or client-file repository. The trigger is rarely a crisis. It is a licence renewal, a Copilot pilot that could not see half the organization's documents, or a records officer who is tired of maintaining two retention systems. It is scoped as one fixed-fee project with a stated end date, delivered by senior US-based engineers from our Orange County, CA base and remote across all US states.
The source you are leaving changes the work far more than the destination does. If your content is in a file sync platform rather than a records system, the awkward parts are different: for a client-facing exchange it is portals, request links and guest access, which our ShareFile to SharePoint migration services handle, and for a plain server it is inventory and wave planning, covered by the file server playbook above. Once the records land, our SharePoint intranet and document management consulting turns the new libraries into a workspace with navigation, views and governance behind it. And because Microsoft 365 Copilot can only be as safe as the permissions underneath it, organizations planning a Copilot rollout want the group and access clean-up finished as part of this move rather than after it.
Related services
Client portals, request links and folder templates rebuilt as external SharePoint sites, guest access or a Power Pages portal.
Approvals, routing and notifications built as flows — the layer that replaces Laserfiche Workflow once the records have moved.
Turn the migrated libraries into a structured intranet with navigation, metadata and permissions people can follow.
The inventory, structure design and cutover playbook for whatever never made it into Laserfiche at all.
Why permissions clean-up is the prerequisite nobody budgets for, and how to do it in the right order.
Why a scoped price beats an open meter when the work has a hard cutover date attached.
FAQ
Integration is the right answer for some estates, and we say so. It keeps two products, two licence bills, two permission models and two places to search. Migration is worth it when the goal is one platform, one retention system and one index for Microsoft 365 Copilot. The free consultation puts both options on paper with their trade-offs.
Each template becomes a SharePoint content type and each field becomes a site column of the matching type: text, date, number, list-driven choice or lookup. Values are carried across document by document, so a record filed under a contract template in Laserfiche is still findable by vendor, effective date and status once it sits in a SharePoint library.
They are rebuilt rather than copied, because SharePoint applies retention through Microsoft Purview labels and policies instead of Laserfiche schedules and cutoff instructions. During inventory we write down every schedule in your own policy language, confirm it with the records officer, configure it in Purview, then prove it against real documents in the pilot before anything moves.
Yes, where the repository holds it. Laserfiche stores document versions where versioning was enabled on the folder, and we export each version in order so SharePoint records the same chain with its original dates and authors. Annotations, redactions and stamps are exported as a burned-in rendition alongside the clean original, so nothing legally visible is lost.
Power Automate and Power Apps. Every workflow definition is read, the ones that still run are listed with their triggers, routing and approvers, and each is rebuilt as a flow. Laserfiche Forms become Power Apps forms or Microsoft Forms depending on complexity. Workflows nobody has triggered in a year are retired by agreement, not rebuilt by habit.
Most projects run two to four weeks and are quoted as one fixed fee after a free consultation. The number is driven by repository size, how many templates and fields carry real metadata, how many retention schedules apply, and how many workflows and forms still run. Thirty days of hypercare follow cutover, and every deliverable lives in your own tenant.
Book a free consultation
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
The fastest way to reach us is the form — tell us the task and we’ll reply within one business day.