Consovenio

Senior SharePoint engineers

SharePoint migration

SharePoint migrations you can audit

Dry run first. Every document accounted for. Nothing breaks on cut-over day.

We move SharePoint Server farms, file shares and whole tenants into SharePoint Online - with metadata, versions and permissions intact, and with a verification report that shows where every single item ended up. Senior engineers who have been doing this since 2010, not a bulk copy.

Start with a Migration Assessment How it works
Moving from
  • Microsoft SharePoint Server
  • Windows file shares and NAS
  • Another Microsoft 365 tenant
  • Google Drive
  • Box
  • Dropbox
Enterprise document management
  • OpenText Documentum
  • OpenText Content Server (Livelink)
  • IBM FileNet
  • Xerox DocuShare
  • Hyland OnBase
  • M-Files
  • HCL Notes / Domino

Why now

Most of these dates are already behind you

Microsoft's calendar for SharePoint has run out. If any of this is still in production, the deadline is not coming - it has passed.

  1. April 2021

    SharePoint 2010

    Extended support ended. No security updates since.

  2. April 2023

    SharePoint 2013

    Extended support ended - for the farm and for its workflow engine.

  3. April 2026

    SharePoint Online clean-up

    SharePoint 2013 workflows, SharePoint Add-ins and Azure ACS sign-in switched off. No extensions.

  4. July 2026

    SharePoint 2016 and 2019

    Extended support ended, together with InfoPath 2013. InfoPath Forms Services removed from SharePoint Online.

  5. Today

    Your farm

    Running without security updates, or carrying forms and workflows that no longer have a future.

Only SharePoint Server Subscription Edition is still supported on-premises, and only while you keep installing its updates.

Security

No more patches for the servers that hold your contracts, policies and HR records. Every new vulnerability stays open for good.

Audit and compliance

Unsupported software is a standard finding under ISO 27001, NIS2 and DORA. "We are planning to migrate" stops being an answer the second time it is asked.

People and integrations

The admins who know the farm move on, and every connection still signing in the old way is one outage away from a crisis. Fixes only get slower and dearer.

Where you are coming from

Typical starting points - and what a project looks like

Every source has its own traps. These are examples of the situations we are usually called into.

Core service

SharePoint Server on-premises

Example: a 2016 farm with 1.4 TB in 60 site collections, a dozen InfoPath forms and three classic workflows that approve contracts. The farm is out of support, and the business cannot stop for a weekend.

Carries over: metadata, versions, authors and dates, permissions, managed metadata, page content.

VersionMicrosoft support
SharePoint 2010Ended April 2021
SharePoint 2013Ended April 2023
SharePoint 2016Ended July 2026
SharePoint 2019Ended July 2026
Subscription EditionSupported, needs regular updates

Every version moves straight to SharePoint Online - no stop-over on a newer farm.

Core service

Windows file shares and NAS

Example: 15 years of a P:\ drive - 3 million files, paths longer than SharePoint allows and folder permissions granted to individual people. The goal is libraries people can find things in, not a copy of the mess.

Carries over: structure by an agreed mapping, dates and owners, permissions translated to Microsoft 365 groups.

Core service

Microsoft 365 tenant to tenant

Example: an acquired company with 400 users moves into the parent's tenant - SharePoint sites, Teams files and everyone's OneDrive, with a cut-over on a Friday evening and working links on Monday.

Carries over: sites, team files and OneDrive content, versions, users and groups mapped across tenants.

Case by case

Google Drive, Box and Dropbox

Example: a team that grew up on a consumer-style cloud drive and is consolidating onto Microsoft 365 - shared folders become team sites, personal files go to OneDrive.

Carries over: files, folders and sharing where the source exposes them. Native Google Docs are converted to Office formats.

Scoped per project

Enterprise document management systems

Documentum · Content Server (Livelink) · FileNet · DocuShare · OnBase · M-Files · Notes / Domino

Example: a regulated company retires a 20-year-old Documentum repository - 8 million documents, custom object types and retention rules, licences renewing next year.

Carries over: documents and versions, attributes mapped to SharePoint columns, cabinet structure, ACLs translated to groups, retention mapped to Microsoft Purview labels.

Product names and logos are trademarks of their respective owners and are used only to identify the systems we migrate from.

Beyond the documents

What gets rebuilt, not copied

Documents move. Customizations do not - the platforms they ran on are gone from SharePoint Online. This is where migrations usually stall, and where we spend most of our engineering time.

On your farm today
In SharePoint Online
SharePoint 2010 and 2013 workflows
Power Automateor a .NET service when the process is too complex for a flow
InfoPath forms
Power Apps or list formsMicrosoft Forms for simple surveys; some forms are simply retired
SharePoint Add-ins
SharePoint Framework (SPFx)web parts and extensions that run inside modern pages
Farm solutions and timer jobs
Scheduled jobs on Microsoft Graphwith logging and alerts, instead of code inside the farm
Event receivers
SharePoint webhooksreacting to changes without code in SharePoint
ACS app secrets, passwords, service accounts
Entra ID apps with certificatesleast privilege with Sites.Selected, owned and revocable by you

Every item gets a decision. The assessment lists each workflow, form, solution and integration with a proposal - rebuild, replace with a standard feature, or retire - and the price of each.

How it works

Five steps, and the dry run is not optional

A typical migration takes 4 to 12 weeks from the signed assessment. Every step ends with something you can check - not just a status update.

  1. 5-10 business days

    Assessment

    Read-only inventory of content, customizations, integrations and permissions. Nothing changes in your environment.

    You getReport, risks, wave plan and a fixed price

  2. 1-2 weeks

    Mapping

    Target sites and libraries, metadata, permission model and naming agreed with you before anything moves.

    You getSigned-off mapping and target design

  3. 1-2 weeks

    Dry run

    Never skipped

    The whole migration rehearsed end to end against the real target, without switching anyone over.

    You getDifference report and fixes, before day one

  4. 2-8 weeks

    Cut-over in waves

    Department by department or site by site, each wave with a short final delta. No big-bang weekend.

    You getWorking sites, users switched wave by wave

  5. about 1 week

    Verification

    Source and target compared item by item: counts, versions, authors, dates and unique permissions.

    You getVerification report and audit trail to keep

What usually breaks

The problems we plan for before they find you

None of these show up in a vendor demo. All of them show up in real migrations - and each one has a step in our process where it gets caught.

Integrations nobody remembered

What users see401 Unauthorized - from a nightly script, the morning after cut-over

Every connection to the farm inventoried, moved to a certificate-based Entra ID app and smoke-tested before the switch.

Caught in Assessment

Paths too long, names not allowed

What users seeThe file name or path is too long - on 40,000 files at once

Renamed by an agreed rule during the rehearsal, and every rename is in the log so people can still find their files.

Caught in Dry run

Permissions nobody understands

What users seeAccess denied - request access, from half the company on Monday

Years of broken inheritance and direct grants mapped to groups, with a report of what changed and why.

Caught in Mapping

Large lists

What users seeThe attempted operation is prohibited because it exceeds the list view threshold

Lists over 5,000 items found up front; indexes, views and filters fixed before users ever see the error.

Caught in Assessment

Links to the old address

What users seeThis site can't be reached - from bookmarks, documents and other systems

Hard-coded links found in documents, pages and integrations, then rewritten or redirected so they keep working.

Caught in Dry run

Lost history

What users seeModified by Migration Account, today - on every single document

Created by, modified by, dates and versions preserved to the depth you choose, and compared item by item at the end.

Caught in Verification

Proof

Where this shows up in our work

Cross-industry

Policy & procedures management platform

A document lifecycle platform for a global investment services group delivering asset servicing solutions: authoring, approval, publishing and adoption tracking of internal policies across ten countries - rebuilt from an on-premises SharePoint farm onto .NET and Microsoft 365.

Read the case study →

Cross-industry

SharePoint to Microsoft 365 migration & auth modernization

Moving decade-old SharePoint estates - content, customizations and the integrations nobody remembered - to SharePoint Online, and modernizing every service connection to Entra ID before Microsoft retired legacy sign-in.

Read the case study →

Cross-industry

Global employee directory

A company-wide people directory for a multinational group: instant search, org charts and office maps, fed directly from HR systems across ten countries.

Read the case study →

Price

Start with a fixed price: $1,950

The Migration Assessment gives you the inventory, the risks, the wave plan - and a fixed price for the migration itself. No per-GB surprises and no open-ended hours. Prices exclude taxes.

Credited in full if you go ahead. Order the migration within 30 days of the readout and the whole assessment fee is deducted from it.

See the Migration Assessment Talk to an engineer

After the migration

We moved it - we can keep it healthy

A new SharePoint Online tenant drifts fast: sharing, owners, storage, guests. The engineers who migrated it can run it for you as SharePoint Admin as a Service, for a fixed monthly fee.

Questions

What people ask before they move

Something not on the list? Ask an engineer - you get an answer from someone who has done the migration, not from sales.

Ask a question
Will the business have to stop?

No. Content moves in waves while people keep working in the source. Each wave ends with a short final delta and a switch-over, usually outside working hours.

How long does it take?

The assessment takes 5-10 business days. A typical migration takes 4 to 12 weeks, depending on volume, customizations and how many waves the business wants. You get the plan together with the fixed price.

Do we keep versions, authors and dates?

Yes. Created by, modified by and dates are preserved, and version history is migrated to the depth you choose - the full history or only the last versions, which is faster and cheaper on storage.

We don't really know what is on our farm.

That is normal, and it is exactly what the assessment is for. Our read-only inventory finds the sites, the volume, the customizations and the integrations - including the ones nobody remembers.

What happens to our workflows and InfoPath forms?

They cannot be copied - the platforms they ran on are gone from SharePoint Online. The assessment lists every workflow and form with a proposal to rebuild it in Power Automate or Power Apps, replace it with a standard feature, or retire it, and a price for each.

Is the $1,950 assessment credited?

Yes. If you order the migration within 30 days of the readout, the whole assessment fee is deducted from it. If you don't, you keep the report, the inventory and the plan - to use with us or anyone else.

Can you migrate from Documentum, FileNet, Google Drive or Box?

Yes. Enterprise document management systems are scoped per project, cloud drives case by case - after we check what the source lets us carry over. Choose the source in the assessment order and we confirm the scope on the first call.

What tools do you use?

Our own migration tooling with an item-level audit database, combined with Microsoft and commercial migration tools where they are the best fit. You get the same verification report either way.

Who can see our data?

Only the named engineers on your project, through accounts and apps you control and can revoke. Processing stays in your tenant and on our EU infrastructure, and we sign your NDA if you have one.

What if we want to stay on-premises?

Then the assessment still tells you what you have and what is at risk. Our focus is SharePoint Online, but we will tell you honestly whether moving is worth it for you - and Subscription Edition is the only supported on-premises option left.

Next step

Not sure what is on your farm? That's what the assessment is for.

$1,950, fixed. Read-only, 5-10 business days, and you leave with a plan and a price - whether or not you migrate with us.

Order the Migration Assessment Ask a question first