Moving content into Microsoft 365
SharePoint Migration Services, matched to where your files live today
Fixed-fee SharePoint migration services from senior US-based Microsoft engineers, scoped by source. A file server, a Dropbox or Box account, an Egnyte appliance, a ShareFile client portal, a Confluence wiki, a Laserfiche repository and an old SharePoint Server farm each break in different places — so each gets its own inventory, destination design and cutover plan. One written price, typical delivery in 2–4 weeks, 30 days of hypercare included.
Representative dashboard — sample data
Pick your starting point
Eight sources, eight different projects
The destination is always the Microsoft 365 tenant you already pay for. What changes from one source to the next is what breaks on the way — and that is what each service below is built around.
File server to SharePoint
Mapped drives, NTFS permissions and fifteen-year folder trees. The work is restructuring, archive decisions and long paths.
Dropbox to SharePoint
Team and member folders, accumulated sharing, and links sent to clients that nobody has audited in years.
Box to SharePoint
Files copy; Box Notes, Relay workflows, metadata templates and Shield classifications have to be rebuilt.
Egnyte to SharePoint
A hybrid estate with a local appliance and a cloud tenant to reconcile, plus CAD-heavy project trees.
ShareFile to SharePoint
A client-facing exchange first: external people, portals and file-request links come before internal folders.
Confluence to SharePoint
Nested page trees, macros and Atlassian permissions — a knowledge-base redesign, not a file copy.
Laserfiche to SharePoint
A records system: templates become content types, retention schedules move into Microsoft Purview, workflows are rebuilt.
SharePoint Server to Online
An out-of-support farm with Designer workflows, InfoPath forms and full-trust customizations to replace.
How it works
The same three phases, whatever the source
- 1
Inventory and design
A free consultation, then a scan of the source: what is live, what is history, who can reach what. You get a destination design, a wave plan, one fixed price and a cutover date in writing.
- 2
Pilot one real team
The destination is built and one volunteer team, site, space or records series moves end to end, so permissions, search and habits are tested on real work before anyone else is affected.
- 3
Waves, cutover, hypercare
Remaining content moves in validated waves with a final pass at cutover. We train your teams, hand over admin documentation, and stay on for 30 days of included hypercare.
What each move involves, side by side
Every route below lands in SharePoint Online and OneDrive, and every one follows the same inventory, pilot and wave rhythm. What differs is the content type, the thing that stretches the timeline, and whether Microsoft's included tooling can do the copying. Microsoft documents the sources its SharePoint Migration Tool supports (opens in new tab); where a source is not on that list, the plan says so up front.
| Source | Scope and data types | What needs a decision or rebuild | Typical timeline |
|---|---|---|---|
| File server | Mapped drives and departmental shares; Office documents, PDFs, scans, years of archive | Restructuring deep folder trees, NTFS permissions to SharePoint groups, what to archive instead of move | 2–4 weeks; archive volume and permission sprawl set the pace |
| Dropbox | Team folders to SharePoint libraries, member folders to OneDrive | External share links (not recreated), version history (latest version only), identity mapping | 2–4 weeks; sharing clean-up sets the pace |
| Box | Files, folders and collaborator access | Box Notes, Relay workflows, metadata templates, Shield classifications and Box Sign are rebuilds | 2–4 weeks; the number of platform features in use sets the pace |
| Egnyte | Cloud folders plus content on a local Storage Sync appliance; often CAD and large binaries | Reconciling two sources of truth, folder permission groups, CAD reference paths | 2–4 weeks; the on-premises half and CAD trees set the pace |
| ShareFile | Client portals, file-request links, internal folders and personal space | Guest access or a portal, reissued external access, retention and signature workflows | 2–4 weeks; the external-access audit sets the pace |
| Confluence | Spaces, nested pages, attachments, labels and blog posts | Macros, page hierarchy expressed as navigation and metadata, Atlassian permissions onto Entra ID | 2–4 weeks; the macro inventory sets the pace |
| Laserfiche | Records with templates, fields, versions, annotations and audit history | Retention schedules into Purview, workflows and forms rebuilt, whether to integrate instead | 2–4 weeks; retention mapping and records sign-off set the pace |
| SharePoint Server | Site collections, content databases, lists, libraries and content types | Designer workflows to Power Automate, InfoPath forms to Power Apps, full-trust solutions to SPFx or retired | 2–4 weeks; the count of customizations sets the pace |
The timeline column is deliberately similar across the board. That is not a template — it is what happens when the inventory and design are done properly first. The detailed week-by-week breakdown, and the things that genuinely stretch a project, are in our guide to how long a SharePoint migration takes.
Data volume matters less than you think
The first question most teams ask is how many terabytes they have. It is a fair question, but it rarely decides the schedule. Microsoft's migration tools run incremental passes, so a large source copies in the background while the waves are planned, and the final pass at cutover moves only what changed since the last run. Raw size becomes the constraint only at the extremes: individual files are capped by Microsoft's 250 GB per-file migration limit (opens in new tab), and very deep folder paths run into SharePoint's 400-character URL limit.
What actually takes time is judgement. How many folders are live work versus archive, how much of the sharing still needs to exist, and how many workflows, forms or macros have to be rebuilt rather than copied. A source that is half archive can shrink dramatically once the archive stays behind on a read-only share with a retirement date, which is usually the single biggest lever on both the schedule and the fee.
Cost factors behind the fixed fee
Every one of these SharePoint migration services is quoted as one written price after a free consultation, never an hourly meter. The fee is driven by the same handful of factors regardless of source: the number of users, sites, spaces or folders that move; how much the destination structure has to be designed rather than copied; how tangled permissions and external sharing have become; and how many platform features need rebuilding on the Microsoft side. Our breakdown of what a SharePoint migration costs a small business walks through those drivers in more detail, and how our fixed-fee process works covers the scoping conversation, the written scope, and the delivery window.
Microsoft's own migration tooling is included with your tenant for the sources it supports, so on most routes you are not paying for a tool licence at all — you are paying for the inventory, the design, the permission mapping and the rebuilds. Confluence is the exception worth knowing about before you budget: it is not a Microsoft-supported source, so that route uses third-party tooling or scripted extraction.
When not to migrate
Some of the most useful consultations end with a recommendation to leave something where it is. A few honest examples:
- A working integration. Laserfiche publishes a SharePoint Online integration. If it is doing its job and nobody is trying to consolidate licences or retention, keeping it is legitimate.
- CAD trees with fragile references. Some engineering project folders depend on exact paths and belong on a file share for now, even when the rest of the estate moves.
- Archive nobody opens. Content untouched for years is often cheaper to leave on a read-only share with a retirement date than to migrate, restructure and re-permission.
- No owner for the destination. If nobody will own the new sites once hypercare ends, fix that first — our SharePoint consulting work on governance and structure is usually the better starting point.
Everything lands in the tenant you own, and nothing in the source is deleted by the migration itself — it copies, so the old system can stay live through the waves and read-only afterwards. The work is delivered by senior US-based engineers from our Orange County, CA base and remote across all US states.
Related services
Planning, budgeting and what comes after the move
SharePoint Consulting
Turn migrated libraries into a structured intranet with navigation, metadata, and permissions people can follow.
SharePoint Migration Timeline
A realistic week-by-week view of inventory, pilot, waves and cutover, and what stretches each phase.
SharePoint Migration Cost
The factors that drive a fixed migration fee for a small business, and where the money actually goes.
FAQ
Questions before you choose a route
Start from where the content lives today, not from the tool. File servers, Dropbox, Box and Egnyte are folder-to-library moves. SharePoint Server is a farm with workflows and forms to rebuild, Confluence is a wiki, ShareFile is a client exchange, and Laserfiche is a records system. Each has its own scoped service.
Typical delivery is two to four weeks from kickoff for every source we cover: about a week of inventory and design, a pilot wave, then the remaining waves and cutover, followed by 30 days of hypercare. Decisions, permissions and rebuilds set the pace far more often than raw data volume does.
The fee follows the work, not the terabytes. It reflects how many users, sites or folders move, how much the destination needs designing, how tangled permissions and external sharing have become, and what has to be rebuilt rather than copied. After a free consultation you get one written price before anything starts.
No. The SharePoint Migration Tool and Migration Manager cover file shares, SharePoint Server and major cloud storage services such as Box and Dropbox at no extra cost. Confluence is not on Microsoft's supported-source list, so that move uses third-party tooling or scripted extraction. No tool makes the design decisions for you.
When the source still does a job SharePoint would do worse. A working Laserfiche integration may be worth keeping, some CAD project trees belong on a file share for now, and archive nobody opens may be cheaper to retire than move. We say so in the consultation rather than sell a project you do not need.
Book a free consultation
Get more from the Microsoft tools you already pay for
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.
- Fixed-fee scope agreed before any work starts
- Senior, US-based Microsoft engineers — no handoffs
- Typical 2–4 week delivery
- 30 days of post-delivery hypercare included
The fastest way to reach us is the form — tell us the task and we’ll reply within one business day.