Your field crews save tickets and safety forms to a shared drive that nobody can search. Head office has a SharePoint site that half the company can’t open and the other half can edit. An approval that used to run through an old workflow stopped working in the spring, and nobody noticed until an invoice sat for three weeks.
We handle this as fixed projects: migrations, document control, permissions and governance, and approvals. Each one has a clear scope and ends with a system your own team can run.
Why 2026 forced the question
Three Microsoft deadlines have passed, and they decide what to fix first.
| What | Date | What it means for you |
|---|---|---|
| SharePoint 2013 workflows in Microsoft 365 | Removed 2 April 2026 | Approvals built on them have stopped running |
| SharePoint Server 2016 and 2019 | Extended support ended 14 July 2026 | Servers still run, but get no security updates |
| InfoPath Forms Services in SharePoint Online | Support ended 14 July 2026 | Forms may still open, but on borrowed time |
The servers didn’t switch off, and some InfoPath forms still submit. That can look like nothing changed. But on unsupported software, a small failure can turn into a long outage.
If you run SharePoint Server 2016 or 2019, the supported paths are SharePoint Online or SharePoint Server Subscription Edition. For forms and workflows, Microsoft points to Power Apps and Power Automate.
What we fix, and how
File server and legacy SharePoint migrations
Migrations usually start from a Windows file server, an old SharePoint 2013/2016/2019 farm, or a legacy document system. Copying the files is the easy part. Whether the project ships on time comes down to four things:
- Sites, libraries, content types and the permission model are designed before anything moves.
- SharePoint Online has a 400-character total URL limit, which catches deep project folder trees.
- Microsoft 365 throttles large moves, so we plan the waves around it instead of discovering it on cutover weekend.
- Every batch is reconciled against the source before anyone signs off.
Copying file-share permissions across as they are usually makes things worse. Our guide on how to migrate a file server without permission sprawl covers the alternative. For the full service, see SharePoint migration services.
Document control with metadata and retention
Field crews and head office rarely agree on where a document belongs, and folders make you pick one place. Metadata lets the same document show up however each group looks for it.
A working document management setup in SharePoint tags each document with the things people actually search by: well or site, AFE or job number, document type, revision status. Retention rules follow the document type, so archiving happens without anyone having to remember it. When a regulator, partner or auditor asks for a specific revision, you can find it.
Read how we design a SharePoint DMS with metadata and retention.
Permissions and governance clean-up
Every “just share it with me” breaks inheritance on another folder. After a few years of that, nobody can say who can see the drilling contracts.
A clean-up project typically covers:
- An inventory of who can access what, including links shared outside the company.
- A simple model: SharePoint groups per site, named owners, inheritance restored where it was broken.
- Rules for creating new sites and Teams, so the mess doesn’t grow back.
- A scheduled governance review, so owners confirm access on a fixed cycle.
After go-live, further help comes as planned work: a governance review, the next migration wave, a new library or approval. Each piece of work is scoped and handed over, so your IT team owns the result.
Power Automate approvals built on SharePoint
Field ticket sign-off, purchase approvals, new hire onboarding and document review mostly start life as a SharePoint list and an email chain. They’re a good fit for Power Automate, with one limit to design around.
A single Power Automate cloud flow run lasts at most 30 days, including time spent waiting on an approval. Design for the approver who is on a two-week hitch with no signal.
Store the approval ID on the list item, handle the response in a separate flow, and re-send expired approvals with a daily flow. See the pattern in onboarding approvals in SharePoint and Power Automate.
If you still have SharePoint 2013 workflows or InfoPath forms, this is where they get rebuilt. The Microsoft 365 Assessment tool lists where InfoPath is still in use, which gives you a scope to start from.
What we’ve delivered
- E.S. Fox, an Ontario industrial fabricator: about 4 TB of legacy DocuShare content moved to SharePoint Online, with documents, metadata and permissions. The information architecture was set before content moved, batches were reconciled against the source, and phased cutovers kept production running. Read the DocuShare case study.
- TD Wealth, Toronto: a two-year engagement moving 1+ TB of SharePoint 2013 content to SharePoint Online in phased waves with validation checkpoints.
Bonanza Drilling, with its HQ in Brooks and an office in Calgary, runs field tickets, HSE checklists and payroll export on Dataverse and Canvas Apps. 25+ paper forms were retired, and pulling a record went from about 30 minutes to instant. See the Bonanza Drilling case study.
What happens after you get in touch
You get a written response within one business day of first contact. If you’re still working out the scope, start with a 45-minute call with a senior consultant. You describe the file share, the site or the approval that’s causing trouble, and we tell you how we’d approach it.
Once the scope is signed:
- Discovery and workshops happen on-site in Calgary, with your field and head office people in the room.
- The build runs remotely, and demos and rollout come back on-site.
- From signed scope to a first usable build is typically four to eight weeks.
Questions Calgary teams ask
What does a SharePoint project with you usually include? One of four things, or a combination: a migration from a file server, older SharePoint or another document system; document control with metadata and retention; a permissions and governance clean-up; or approvals rebuilt in Power Automate. Each is scoped up front with a defined handover.
We’re still on SharePoint Server 2016 or 2019. What are our options? Extended support ended on 14 July 2026. You can move to SharePoint Online, or upgrade to SharePoint Server Subscription Edition if you need to stay on-premises. We help you pick based on your content, integrations and compliance needs, then plan the migration in waves.
What happens after go-live? We hand over documented sites, owners and governance rules. Later work, such as governance reviews, further migration waves or new approvals, is scoped as its own project.
If your shared drive, old farm or broken approvals are holding up the work, we can scope the fix with you.