Access database to web application without losing what it quietly does.
That .accdb on the shared drive runs quoting, inventory or member records - and the macros and VBA inside it encode rules nobody wrote down. We document what it does, move the data to a managed database, and rebuild the forms and reports as a secure web app your team can reach from anywhere.
Reply within one business day · Written scope and fixed price before any work starts
A fixed-scope service with published price bands - not a SaaS product.
Status as of November 2026. How we label products
Tables
48
Forms in daily use
17 of 62
VBA modules
23
4,180 lines
File size
1.71 GB
of 2 GB limit
Most-used objects
| Object | Type | Used by | Logic found | Decision |
|---|---|---|---|---|
| frmQuoteEntry | Form | Sales (6) | Price breaks, margin check | Rebuild |
| qryOpenOrdersByRep | Query | Managers | Joins 5 tables | Rebuild as report |
| modEmailInvoices | VBA module | Office (1) | Outlook automation | Scheduled job |
| frmOldPricing2014 | Form | Nobody (last opened 2019) | - | Retire |
Rules extracted for sign-off
- Quotes over $25k need manager approvalfrmQuoteEntry · BeforeUpdate
- Quote numbers reset each JanuarymodNumbering
- Discount capped at 12% for repsConfirmed by owner
Tables mapped
41 / 48
Type fixes
63
Orphan records
214
Attachments extracted
9,406
Mapping exceptions
| Access table.field | Issue | Target | Rule | Status |
|---|---|---|---|---|
| tblQuotes.QuoteDate | Text field, 3 date formats | quotes.quoted_on (date) | Parse; 12 manual | 12 to review |
| tblQuoteLines.QuoteID | 214 lines with no quote | quote_lines | Archive orphans | Owner to confirm |
| tblCustomers.Phone | Mixed formats | customers.phone | Normalize to E.164 | Approved |
| tblDrawings.File | OLE object | File storage + link | Extract as PDF | Done |
Tables passing
47 / 48
Rows migrated
1,284,955
Open quote value
$0.00 diff
Parallel run
Day 6 of 10
Checks
| Check | Access | Web app | Difference | Status |
|---|---|---|---|---|
| Customers | 4,812 | 4,812 | 0 | Pass |
| Quotes | 38,406 | 38,406 | 0 | Pass |
| Quote lines | 402,117 | 401,903 | 214 | Orphans archived |
| Open quote value | $2,914,880.00 | $2,914,880.00 | $0.00 | Pass |
In short
Agenbord Migrate for Microsoft Access and FoxPro is a fixed-scope service that turns desktop databases into secure web applications. We inventory the tables, queries, forms, reports, macros and VBA, move the data to a managed SQL database, rebuild the screens and logic as a web app with roles and audit history, and reconcile every table before cut-over. It is a service programme with published price bands, not a software product.
What slows access & foxpro databases down today.
"Unrecognized database format" on a Monday morning
Five people open the shared .accdb over the network, a laptop drops off Wi-Fi mid-save, and the file needs Compact and Repair - or a restore from last week's copy. Multi-user Access over file shares is fragile, and the more the business grows the more often it happens.
Nobody can use it from outside the office
Sales wants quotes on a tablet, the warehouse wants a phone screen, a branch office wants in. Today that means remote desktop sessions, VPNs and copying the file around - each one another security and support headache.
Running on software that's out of support
Access 2016 and 2019 lost Microsoft support on October 14, 2025; Visual FoxPro 9 lost it in 2015. The database still opens, but security fixes have stopped, and the person who understands the VBA retires next year.
How the work flows through the system.
Each workflow runs on one shared record, so nobody re-types numbers between steps.
Discovery: what the database really does
Agenbord → database owner → daily users
- We inventory every table, relationship, query, form, report, macro and VBA module, with row counts and last-modified dates.
- We watch the main users work for a day and list the workflows, including the "run this query, then paste into Excel" steps.
- Hidden business rules in VBA and macros (pricing, numbering, validation, emails) are documented in plain English for sign-off.
- Unused objects are marked for retirement so the new app doesn't rebuild dead weight.
Data migration with type and quality fixes
Agenbord → database owner
- Tables are mapped to a normalized schema in PostgreSQL or SQL Server, including fixing text fields that hold dates or numbers.
- Orphaned records, duplicates and broken relationships are listed for the owner to resolve or accept.
- Attachments and OLE objects are extracted to file storage with links preserved.
- Test migrations repeat until row counts, totals and key relationships match for every table.
Web app rebuild, parallel run and cut-over
Agenbord → users → owner
- Core forms and reports are rebuilt as web screens that work on desktop and phone, with roles deciding who sees and edits what.
- VBA rules become tested server-side code; outgoing emails and exports are rebuilt as scheduled jobs.
- Users run the old database and the web app in parallel on real work for an agreed period.
- On cut-over the Access file becomes read-only, the final data delta is migrated and we stay on hand through the first weeks.
What's included in Agenbord Migrate: Microsoft Access & FoxPro.
Object inventory
Every table, query, form, report, macro and VBA module catalogued with usage and dependencies.
Business-rule extraction
Rules hidden in VBA and macros written up in plain English and signed off before rebuild.
Managed SQL database
PostgreSQL or SQL Server with backups, point-in-time restore and real multi-user concurrency.
Web forms and reports
The screens people use daily, rebuilt for browser and phone, with the same fields and fewer clicks.
Roles and permissions
Sign-in with your Microsoft 365 or Google accounts, roles per screen and field, and multi-factor authentication.
Audit trail
Who changed which record, when, and what the old value was.
Exports and integrations
The Excel exports people rely on, plus API connections to accounting, email or other systems.
Reconciliation reports
Row counts, totals and relationship checks per table, for sign-off before cut-over.
AI that does specific jobs and shows its work.
Every AI feature is tested on your own records before it's switched on, and a person approves anything that moves money or goes to a customer.
VBA and query explanation
Reads VBA modules, macros and SQL queries and drafts a plain-English description of what each one does, including the conditions and side effects. Limits: drafts are reviewed by our engineer and confirmed by the database owner; we write tests from the confirmed rules, not from the AI's reading.
Who it's for and who it isn't.
A good fit if you are
- Businesses running daily operations on an Access database shared over a network drive or remote desktop
- Teams still maintaining a Visual FoxPro application, often written by someone who has since left
- Offices where the database corrupts, locks or slows down when several people use it at once
- Organizations that need staff, field workers or clients to use the system from outside the office
Probably not the right fit if you are
- Single-user Access databases that work fine and hold nothing sensitive
- Teams who mainly need a bigger back end - splitting the database and moving tables to SQL Server can be enough
- Projects where a packaged product already covers the whole workflow - we'll point you to it
Designed around the rules you work under.
Plain-English notes, not legal advice. Software supports your compliance process; it doesn't replace your attorney, CPA or compliance lead.
Office 2016 and 2019 support ended October 14, 2025
Microsoft ended support for Office 2016 and Office 2019 - including Access 2016 and Access 2019 - on October 14, 2025, meaning no more security fixes or technical support for those versions. Microsoft - End of support for Office 2016 and Office 2019.
Visual FoxPro has been out of support since 2015
Microsoft's lifecycle page lists Visual FoxPro 9.0 extended support as ending January 13, 2015. There is no supported path forward on the platform itself. Microsoft Lifecycle - Visual FoxPro 9.0.
Access size limits
An Access database file is limited to 2 GB including system objects. Linked back-end files can stretch that, but each is still capped. The managed SQL database removes the ceiling. Microsoft - Access specifications.
What exists today and what's being built.
Runs in production today
Capabilities of the engine this edition is built on.
- Fixed-scope programme: assessment, data mapping, test migrations, reconciliation, cut-over and hypercare
- Web, desktop and mobile apps with role-based access, as used in our production engines
What this edition adds
In development with design partners.
- Access object inventory and VBA documentation templates
- FoxPro .dbf extraction scripts
- Reusable web app starter with roles, audit trail and exports
Connects to the systems you already run.
Systems we integrate with
Named platforms are examples we build against through their public APIs - not partnership claims.
How it compares - honestly.
Established products are often the right answer. Here's when each one is the better choice.
| Product | What it is | The better choice when |
|---|---|---|
| Microsoft Power Apps with Dataverse | Microsoft's low-code platform for building business apps on Microsoft 365, often suggested as Access's successor. | You are standardized on Microsoft 365, the app is fairly simple, and you have someone in-house to maintain low-code apps. |
| Caspio | A low-code online database platform with a long history of hosting former Access applications. | You want to rebuild the forms yourself on a hosted platform and accept its subscription and design constraints. |
| Access front end with a SQL Server back end | Keeping Access forms while moving tables to SQL Server or Azure SQL - Microsoft documents this upsizing route. | Everyone works in the office on Windows, the forms are fine, and the real problem is the data file's size or corruption. |
What it costs, up front.
Migrations are fixed-price after an assessment. Price depends on the number of forms and reports in daily use, the amount of VBA logic, data quality and the integrations needed.
Assessment
From $2.5k
Object inventory, workflow observation, business-rule summary, recommended target (including keep-and-upsize if that's enough) and a fixed quote.
1–2 weeks
Standard migration
$10k–$40k
One database with up to roughly 30 working forms and reports rebuilt as a web app, data migrated and reconciled, roles, audit trail and cut-over.
4–10 weeks
Complex migration
$40k+
Several linked databases or a FoxPro system, heavy VBA logic, integrations with accounting or ERP, or client-facing portals.
Phased
Access & FoxPro databases: common questions.
Does Access stop working now that support has ended?
No. Access 2016 and 2019 still open and run, but since October 14, 2025 Microsoft no longer provides security fixes or support for them. Newer Access versions in Microsoft 365 are still supported, so end of support alone doesn't force a rebuild - corruption, remote access and security usually do.
Can't we just move the tables to SQL Server and keep Access?
Sometimes that's the right answer, and we'll say so. Splitting the database and moving tables to SQL Server fixes size and much of the corruption risk. It doesn't give you browser or phone access, and every user still needs Access installed on Windows.
What happens to all the VBA code?
We read it, document the business rules in plain English, and confirm them with you. The rules are then rebuilt as tested server-side code. Code that turns out to be unused or obsolete is retired, with your agreement.
We have a FoxPro system. Can you move that too?
Yes. FoxPro tables (.dbf) are extracted and migrated the same way, and the application logic is documented from the source code. FoxPro projects are usually in the complex band because the code tends to be larger and older.
How is the web app more secure than our database on a shared drive?
Users sign in with their own accounts and multi-factor authentication, roles limit what each person can see and change, every edit is logged, the data is encrypted and backed up with point-in-time restore, and nobody can copy the whole database to a USB stick.
Who owns the new application?
You do. You get the source code and the database, hosted in your own cloud account or ours under a support plan.
Sources
- Microsoft - End of support for Office 2016 and Office 2019
- Microsoft Lifecycle - Visual FoxPro 9.0
- Microsoft - Access specifications
Regulatory notes are plain-English summaries, not legal advice.
Service programme
Get a fixed price for your migration.
Tell us what you're moving from and to. We'll reply within one business day with next steps for an assessment and a written, fixed quote.
Other editions of Agenbord Migrate.
Microsoft Dynamics GP users
Agenbord Migrate: Dynamics GP
Plan a Dynamics GP replacement before Dec 31, 2029: Business Central, Acumatica, Sage Intacct or custom, with data migrated and reconciled. Fixed price from $10k.
View productQuickBooks Desktop users
Agenbord Migrate: QuickBooks Desktop
Fixed-price QuickBooks Desktop migration from $10k: to QuickBooks Online, an industry ERP or a custom system, with mapped data and reconciled balances.
View productBusiness-critical spreadsheets
Agenbord Migrate: Spreadsheets to Web App
Fixed-price service from $10k to replace business-critical Excel or Google Sheets with a web app: roles, approvals, audit trail and integrations.
View productGuides and services for this decision.
Buyer's guides
Related services
Looking for a different industry? Browse all products.
