Rule-Preserving Visual FoxPro Migration Services

Move the rules your business runs on, not just the tables.

The Visual FoxPro application still does its job. It schedules visits, prices orders, tracks specimens or posts charges, and it has done so for many years. But Microsoft ended support for Visual FoxPro 9.0 in 2015, the people who understand the code are retiring, and every change takes longer and costs more than the last one.

Most Visual FoxPro migration programs do not fail on the target platform. They fail because the business rules live inside forms, program files and report layouts that nobody documented, and a tool that converts the tables leaves those rules behind. The data moves and the behavior quietly changes.

Cabot works rules first. We inventory the application, write tests that record what it does today, move the data to SQL Server or PostgreSQL, rebuild the logic in C# and .NET, and run old and new side by side until the numbers match. Your team keeps working on the system it knows while the new one earns its place.

Tell us about your Visual FoxPro application

Share the VFP version, the rough size of the data and what the system runs. An engineer replies with the first scoping questions.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

No obligation. Your details stay private.

What Visual FoxPro migration actually involves

Visual FoxPro migration is the move of a VFP application, its DBF data and its business rules to a supported platform, usually C# and .NET with SQL Server, without losing the behavior the business depends on.

That separates it from four things it is often confused with. Keeping the runtime leaves the application exactly where it is and fixes nothing. Wrapping puts a new interface or API around old code that still has to be maintained. Automated code conversion translates program files line by line and often produces C# that reads like FoxPro and that nobody wants to own. A full rewrite starts from a blank page and has to rediscover every rule the old system quietly enforced. A sound FoxPro migration keeps what the system does, changes what it runs on, and treats proof that the new system behaves like the old one as the deliverable.

In practice some parts move and some are rebuilt. Tables, indexes and records move to SQL Server or PostgreSQL, with the data cleaned and reconciled on the way. Forms, reports, menus and program logic are rebuilt, because a Visual FoxPro form mixes screen, rules and data access in one file. Third party controls and COM or ActiveX components are replaced or isolated. Whether the target is a web application, a desktop client or an API, a Visual FoxPro to .NET move follows the same order: rules first, then data, then screens.

Migrating is not always the right call this quarter. A small, stable application with one owner, no regulated data and a person who still knows it can stay where it is while you plan. When the system holds patient or member data, sits on a server nobody wants to touch or depends on one retiring developer, the risk grows each month the decision waits. The assessment is built to tell you which case you are in, in writing.

Why Visual FoxPro systems stall before they move

These are the six reasons technology and operations leaders give when a FoxPro migration slowed down or never started. Most are decided in the first weeks, before anyone writes code.

Two colleagues at a desktop computer reviewing an older business application together

The Visual FoxPro migration services we deliver

Our Visual FoxPro migration services come in six parts, and most engagements use all of them in a sequence set by the assessment. Some organizations need the full path from inventory to retiring the VFP runtime. Others need only the data moved first, or only the reports rebuilt. We give you our recommendation and our reasoning before you commit to anything.

Each part produces something you can inspect: an inventory, a reconciliation report, a test suite that pins current behavior, a working screen, a staged release. Testing and security run inside every part instead of sitting as separate lines.

What does Visual FoxPro migration cost, and what moves the number?

Five things set the cost: the size of the codebase and how many forms and reports it carries, the volume and quality of the DBF data, how much of the business logic is undocumented, the number and age of the integrations, and how long old and new have to run side by side. Two FoxPro applications that look alike on paper can differ many times over, so any figure quoted before an assessment is a guess. Model a range in a few minutes, then tell us what you run and we will scope it properly. We would rather give you a narrow range you can plan around than a wide one that protects us.

What does a Visual FoxPro assessment tell you before you commit?

A short assessment answers the questions that sink most FoxPro migrations before any code changes. It runs in four parts, in this order, and it can end in a recommendation to leave the system alone for now.

Scope your own application: send us a short description of what you run and we will tell you what the assessment would cover.

What does AI actually change in a FoxPro migration?

It changes how fast the slow parts go and leaves the judgment where it was. Reading program files that nobody documented, drafting a plain language list of the rules they enforce, mapping how tables relate and which forms touch them, and finding dead code are all work a model can draft quickly. Deciding which rules the business still needs, which were workarounds for limits that no longer exist and whether a screen should survive at all is not.

The saving concentrates in three places. Discovery goes faster, because a model can summarize an unfamiliar codebase into rules and dependencies for an engineer to check. Test writing goes faster, because characterization tests that record current behavior can be drafted from the code and then run against real data. Translation of repetitive routines goes faster, because a model can propose the same pattern in C# across hundreds of files for review, which is where a FoxPro to C# move spends much of its time.

The risk runs the other way. A model can describe a rule with confidence that the code does not implement, and it can miss behavior hidden in a report expression, a trigger or a setting. So every recovered rule is confirmed against real outputs and against the people who use the system before it counts.

AI shortens the slow parts of a migration. It does not decide which rules survive, approve a merge or sign off a cutover. Those stay with senior engineers and with you, and where you need help choosing a model your policy allows, our AI development team is part of the conversation.

Three commitments hold on every engagement. Our process is model neutral, so we use the model your policy allows. A senior engineer reviews every change before it merges. And we never train any model on your code or data. Test data is synthetic or masked, so protected health information stays out of model prompts.

What we move your FoxPro system onto, and the tools we use to move it

Three layers of tooling, chosen against your environment and your team's ability to run the result rather than against our preferences. The target follows what your security team will accept and what your staff can maintain, and we recommend on evidence from the assessment. Our QA and testing practice builds the test suites that compare the new system with the old before anyone relies on it.

What we work in:

Target platforms

C#
.NET
ASP.NET Core
React
TypeScript
Entity Framework

Data and hosting

SQL Server
PostgreSQL
Azure SQL
Azure
AWS
Docker

Delivery and AI tooling

GitHub Copilot
SQL Server Integration Services
xUnit
Playwright
GitHub Actions
SonarQube

Where AI sits at each stage of a FoxPro migration, and where it does not

Each stage below has an output you can inspect and a person who approves it. Nothing an AI drafts reaches your data, your code or your production system without a named engineer accepting it first.

Migration stage What AI does What stays human Tools used
Assessment Reads program files, forms and report expressions and drafts a plain language list of the rules, data relationships and dependencies they contain Confirming which rules the business still needs and which were workarounds GitHub Copilot, SonarQube
Safety net Drafts characterization tests that record what the application does today, using real outputs as the reference Choosing which behaviors must never change and approving the tests GitHub Copilot, xUnit, Playwright
Translation Proposes C# versions of repetitive routines and drafts DBF to SQL data scripts for review Approving every merge and every data move GitHub Copilot, SQL Server Integration Services
Cutover Compares outputs from the old and new systems and summarizes the differences Accepting or rejecting each difference and approving each cutover Playwright, GitHub Actions

The last column names the tools, so a security reviewer can see exactly what touched the work. Where your policy limits which tools can be used, the same stages run with the tools you allow and the same human review.

How a Cabot FoxPro migration differs from a typical vendor's

Visual FoxPro migrations succeed or fail on rules, data and cutover, not on the choice of target platform. Those are the places projects go wrong, so each row below is a moment where the approach changes the outcome.

Dimension Typical vendor Cabot
Starting point A quote after a short call A written inventory and assessment before you commit
Business rules Left inside converted code or rediscovered in testing Recovered, written down and confirmed by the people who use the system
Data migration Tables copied as they are Profiled, cleaned and reconciled, with keys and constraints designed
Forms and reports Converted automatically or dropped Rebuilt, with report output compared against the old system
Testing Tests written after the build Characterization tests that pin current behavior first
Cutover method One weekend switch One workflow at a time, with old and new running side by side
Rollback Restore from a backup A rollback plan at every stage, rehearsed before it is needed
Knowledge transfer A handover document at the end Your engineers in standups and reviews from week one

Ask any vendor when they would advise against migrating. A credible answer comes quickly and names the conditions. Ours is written into each assessment.

The healthcare organizations we migrate Visual FoxPro systems for

We deliver Visual FoxPro migration services for three kinds of healthcare organization. Each card says what we understand about that environment, rather than claiming coverage of it.

Across all three the pattern is the same: the application is important enough that a failed cutover is not an option, and old enough that few people hold the whole picture. Where the new platform needs a rebuilt application around it, our healthcare application development practice carries the same discipline into the build.

Industries we already understand

volunteer_activism

Healthcare

shopping_cart

Ecommerce

paid

Fintech

apartment

Travel and Tourism

Client Success Stories

See all Cabot case studies

What a migrated FoxPro system has to prove before it goes live

Security leads every Visual FoxPro migration, because the move is your chance to close what the old system never covered. We apply authentication and role based access, encrypt data in transit and at rest, log every change to an audit trail, hold secrets outside the code and scan dependencies and fix known vulnerable ones first. Protected health information stays out of test data and model prompts.

Where the system handles patient data, we map who can see what, scope the work to the safeguards your compliance team requires through our HIPAA compliance consulting practice, and document each control the migration touches. For each stage you receive evidence, not assurance: the test results, the reconciliation report, the list of changes with the engineer who approved each one and the plan for returning to the old system.

Role based access
Authentication and session control
Encryption in transit and at rest
Audit logging of every change
Secrets management
Dependency and vulnerability scanning
Synthetic and masked test data
HIPAA aligned controls
SOC 2 aligned controls

How does a Visual FoxPro application move without the business stopping?

Six steps, each ending in a decision you make rather than a document you receive. Most engagements begin with the first two steps alone, so you can judge the plan and the working relationship before committing to the migration.

Start with step 01: tell us what the application does and we will scope the inventory.

Who owns each part of a Visual FoxPro migration at Cabot

Accountability is explicit from the first day. A solution architect owns the target design and the order of migration, and answers for choices that are expensive to reverse. A business analyst owns the recovered rules and confirms them with the people who use the system. A data engineer owns the DBF to SQL move and the reconciliation that proves it. Senior engineers own the C# and .NET work and the merge reviews. A QA automation engineer owns the characterization tests and the comparison between old and new. A delivery lead owns the schedule and tells you plainly when something slips.

Our depth is greatest in four places: reading code nobody documented, writing tests that pin down behavior before anything changes, moving file based data to a database server without losing integrity, and running old and new side by side until the numbers match.

If you are searching for a Visual FoxPro developer or a FoxPro developer, you are probably trying to keep the system alive or to find someone who understands it. A single contractor leaves the same key person risk in place. Our answer is a team that recovers what the code knows, moves it to a platform with a deep talent pool, and joins your standups and reviews from week one, so the knowledge stays with you. Where a larger group fits, we staff an embedded engineering pod inside your delivery cadence.

Why healthcare technology leaders choose Cabot for rule-preserving Visual FoxPro migration services

A FoxPro migration is easy to start and hard to finish well. These are the six reasons buyers give when they explain why the work sits with us.

Where to go next, depending on what you run

Visual FoxPro migration is one of several specific moves. Which page helps next depends on where your system sits today, and it is usually one of three.

Our Clients

Questions technology and operations leaders ask before starting

  1. How do you migrate Visual FoxPro to .NET?
    We inventory the application, recover its business rules, pin them with tests, move the DBF data to SQL Server or PostgreSQL and rebuild the logic and screens in C# on .NET. Old and new run side by side until the outputs match, then each workflow is cut over with a rehearsed rollback. This is a Visual FoxPro to .NET migration in stages, not a one weekend switch.
  2. Can you migrate FoxPro to SQL Server without losing data?
    Yes, when the data is profiled first and every run is reconciled. We fix quality problems at the source, migrate in rehearsed runs and compare record counts and totals against the DBF tables at every step, with a rollback for each run. Nothing is retired until the numbers match, and a FoxPro to SQL Server move should target a version that Microsoft still supports.
  3. Is Visual FoxPro still supported by Microsoft?
    No. Microsoft ended support for Visual FoxPro 9.0 in 2015 and has not released a new version since 2007. Existing applications can keep running, but there are no security fixes, no vendor support and a shrinking pool of people who know the platform. That gap is the main reason organizations plan a migration.
  4. Should we convert FoxPro to C# or rewrite the application?
    Convert the rules, not the code line by line, and rewrite only the parts where the design itself is the problem. Automated conversion often produces C# that mirrors FoxPro habits and is hard to maintain, while a blank page rewrite loses rules nobody wrote down. A FoxPro to C# move works best when rules are recovered and tested first, then rebuilt cleanly.
  5. What happens to my FoxPro forms, reports and business rules?
    Forms and reports are rebuilt, and the business rules are recovered from the code and carried across as tested behavior. A Visual FoxPro form mixes screen, rules and data access, so we separate them, confirm each rule with your staff and compare the new report output with the old. The rules are the asset, and the migration treats them that way.
  6. How long does a Visual FoxPro migration take?
    It depends on the size of the codebase, the number of forms and reports, the data volume, how much logic is undocumented and the number of integrations. The assessment comes first and gives you a range for the rest, so you see a timeline before you commit. The migration itself runs in staged releases, usually over months, with the old system working throughout.
  7. How much does a FoxPro migration cost?
    Cost follows five drivers: codebase size and the number of forms and reports, data volume and quality, undocumented logic, the number of integrations, and how long old and new run side by side. We give a range after the assessment, so you see numbers before you commit. For a first view, use the cost calculator.
  8. Where can I find Visual FoxPro developers, and do I need one?
    Experienced Visual FoxPro developers are hard to find and often work alone, so hiring one keeps the key person risk in place. Most organizations are better served by recovering what the code knows and moving it to a platform with a deep talent pool. Cabot staffs an engineering team that does both, and joins your own people from the first week.