Move MS Access Database Online with Sharepoint

A services company in the oil industry in Alberta, Canada was using an Access database that was working well for them. They wanted to move this database online to Sharepoint, so they could utilize the database in multiple locations. There are a lot of options to make an online database. We can help you understand the best option for your needs. The tricky part of this project was to convert all the data macros the original developer put on a few tables. This is a big problem with Microsoft template db’s. These are nice if you use them exactly the way they are built, with no need to customize (which is rare). But unfortunately, they are very difficult to customize.

Once the table macros were reworked, field offices in Alberta could update the same lists head office relied on without emailing spreadsheets back and forth. Access stayed in the picture for the heavier reporting and forms their managers already knew. SharePoint handled the shared data. That hybrid setup is what many multi-location clients end up with.

This was an 8-hour project because the database was already working. The time went into untangling template macros, not rebuilding from scratch. If your Access file came from a Microsoft template and you need to change how it behaves, expect that kind of cleanup before any online move.

Moving online is not one-size-fits-all. SharePoint, split database on a server, and other options each fit different teams. We will walk through how many users you have, where they sit, and what must stay in Access before recommending a path. No sales pitch for the wrong architecture. Other hosted options are covered in other ways to put Access online.

Most teams do not publish the whole ACCDB into SharePoint. The usual pattern is to put shared tables on SharePoint lists, keep Access as the front end, and link those lists so field staff and head office edit the same records. Forms, queries, and reports that already work stay in Access. That is how a multi-location shop gets an online backend without throwing away years of form design.

SharePoint list linking has limits you should know before you start: lookup columns, list item caps, and offline use behave differently than a local ACCDB. If your oilfield or warehouse crew works with poor connectivity, we test that path first. If SharePoint is the wrong fit, we say so and look at a split database, Azure SQL, or hosted Access instead.

Microsoft template databases often store business rules as table data macros. Those macros do not move cleanly when tables become SharePoint lists. We rewrite that logic as Access VBA, validation rules, or SharePoint/Power Automate flows—whichever matches how your users actually enter data. That conversion is usually the real project, not the list mapping itself.

Send a copy of the ACCDB (not the only production file), Access version, SharePoint site type (Microsoft 365 or on-prem), user count, and whether data macros or VBA already run on those tables. We review the file, flag template traps, and quote hours at $90/hr with a one-hour minimum. Straightforward hybrid moves can land in a single workday; tangled templates take longer because the macros have to be unwound first.

Call 385-386-3860 or use the form below. We work remotely with US and Canadian clients, including multi-site operations that need the same lists in more than one province or state.