It is necessary to migrate the current working program from FoxPro to C#.

Hello, Viktor! The categories chosen are absolutely correct. Your task is not just a linear migration from FoxPro; it is actually about designing and developing a new custom ERP platform based on C# (.NET). The task is large-scale but architecturally very interesting.

I have a great background in .NET/C# and designing relational databases. I suggest not trying to do everything blindly but to divide the project into clear stages. Right now, I am focusing on the First Stage: Technical Audit and Architecture Design.

What I will implement within the first stage:

Business Logic Analysis (Point 1): Together with your support specialists, I will conduct a complete review of the FoxPro source code, create lists of modules for transfer, and filter out outdated "junk."

Core and Configurator Design (Points 2, 3): I will develop the architecture of the desktop solution (WPF or AvaloniaUI for the speed of heavy forms). To implement an analogue of 1C (Core + Configuration), we will lay down a mechanism for dynamic compilation through the Roslyn API or integrate a scripting engine so that you can extend the program without recompiling the core.
…
Database Migration: I will create a scheme for transferring data from DBF to a modern network database (PostgreSQL or MS SQL) with consideration for query optimization using Entity Framework.

Testing Strategy (Point 4): I will lay down the architecture for Unit tests for business logic (core) and integration tests for data.

Show original

Translate

We already have a nearly ready architectural base for migrating legacy accounting systems to C#, and we can quickly adapt it for your FoxPro project and complete the first stage here on the marketplace. ))

Regarding timelines - the audit, migration map, architecture of the new solution, database strategy, tests, and documentation will take approximately 15 working days.

As for tests - the entire program can be covered by tests, but it makes more sense to divide it into levels - critical business logic, data migration, heavy forms, permissions, network mode, regression before the focus group.

For the architecture, I would go through a separate core, configuration module, data access layer, migration log, automated tests, and a clear update mechanism so that the new system does not just become FoxPro in a different shell. =)

We are in touch here, and we can discuss it right now within the project.
…
I would like to clarify two things.

- How many modules and forms are there approximately in the current program?
- Is the database currently DBF or is there a separate database server, and what is the volume of data that needs to be migrated?

Similar complexity corporate systems.

- https://business.ingello.com/iks - accounting and management system with business logic and roles.
- https://business.ingello.com/forma-bpm - corporate platform for processes, modules, and logic configuration.

The main profile of Ingello for projects on the marketplace - https://systems-fl.ingello.com

Show original

Translate

Hello, I am interested in your offer and would be happy to work on your task. Please provide more details in private messages regarding the project. I look forward to your positive response.

Show original

Translate

Hello How are you today?

Your project is not simply a migration from FoxPro to a modern platform it is effectively the design and development of a new enterprise system based on existing business logic. I understand the importance of preserving functionality while creating a maintainable, scalable architecture for future development.

My proposed approach:

Phase 1 Analysis and Audit

• Analyze the FoxPro source code, database structure, modules, and business processes.
… • Interview current support specialists and key users.
• Identify obsolete functionality and prepare a detailed migration map.
• Document all existing modules, dependencies, reports, and workflows.

Phase 2 Architecture Design

• Design a modern architecture with clear separation between Core and Configuration layers, similar to the 1C approach.
• Define technology stack, database strategy, deployment model, security model, and update mechanism.
• Design desktop and server interaction for high-performance operation over a local network.
• Prepare technical specifications and development roadmap.

Phase 3 – Development and Migration

• Implement the core platform.
• Migrate business logic module by module.
• Create data migration tools.
• Implement role-based access control, logging, and configuration management.

Phase 4 Testing and Documentation

• Unit tests and integration tests where applicable.
• Automated testing for critical business processes.
• User acceptance testing with a focus group.
• Complete technical and user documentation.
• Support, deployment, and maintenance guidelines.

Regarding testing, it is possible to achieve high coverage of the business logic and critical workflows. However, after the analysis stage, I would provide a realistic testing strategy based on the actual complexity of the legacy codebase.

I have experience working with complex business systems involving accounting, inventory management, workflow automation, and ERP-style architectures where long-term maintainability and modularity are critical.

A precise estimate can only be provided after reviewing the FoxPro source code, database structure, number of modules, and business requirements.

I would recommend starting with a paid technical audit and architecture phase. This minimizes risks and provides a clear roadmap before committing to full-scale development.

Thank you

I have confident

Good day, Viktor, I would like to see your program for further actions. Please write to me privately.

Show original

Translate

I will take it on. Over 15 years of experience in various subject areas. Extensive expertise in developing custom accounting solutions. I delve deeply into the essence and logic of the original task, guaranteeing quality implementation. We will sign a contract, and I provide warranty support. Real deadlines and costs will be discussed after a detailed discussion of the technical specifications, feel free to message me.

Show original

Translate

Good day.
I have over 4 years of experience in commercial development on .NET. I am ready to conduct an audit of the current system on FoxPro, prepare a migration plan, the architecture of the new solution, and implement the transfer to C#.
For an accurate assessment, I suggest starting with an analysis of the existing system and the source code. After that, I will be able to provide exact timelines, costs, and an implementation plan.
I would be happy to discuss the project details.

Show original

Translate

I have a ready-made cross-platform desktop framework (Java) that reads the database configuration and builds the logic, interface, etc. Many industry-specific accounting solutions have been developed on it.

Show original

Translate

Hello, Viktor! The task of migrating the accounting system from FoxPro to C# is large-scale and architecturally interesting. I have experience with .NET and developing tools for processing text/script structures, which is critical for creating an analogue of a "configurator".

Projects of this level are not done in one stage. I propose to divide the work, and my current rate is indicated for the First technical stage (Analytics and Architecture), which will include:
1) A complete audit of the FoxPro logic (together with your support specialists), forming a list of modules for transfer.
2) Development of the core architecture in C# (WPF/.NET) considering network operation and dynamic loading of configurations.
3) Designing a new relational database (transition from DBF to MS SQL or PostgreSQL) and creating a migration plan without stopping processes.

The project will be covered by Unit tests at the business logic level (core) and integration tests to check data synchronization. Upon completion of the stage, you will receive ready technical documentation and a prototype for testing by a focus group.

… Questions for clarification:
— How large is the current database (number of tables/volume)?
— Are you considering using ready-made solutions for modularity (for example, Prism or MEF in .NET), or should the core of the configurator be written completely custom?
— What is the approximate overall deadline for the complete replacement of the system?

In my portfolio on GitHub, there are examples of work with data architecture and processing of language/structural components (I can provide links in private messages). I suggest moving to chat for detailed discussion of the technical specifications.

Show original

Translate

Hello! Your project caught my attention. I am ready to start working and ensure high quality execution.

Show original

Translate

Hello! I have reviewed your task and believe that I can successfully complete it. I would be happy to collaborate, please write to me personally for further details.

Show original

Translate

Good afternoon. I propose to develop a desktop application in Python + (PyQt6 or DearPyGui). The database can be local using SQLite or, if it needs to work over a network, it would be better to use a remote one via PostgreSQL. In PyQt6, the program can be covered with tests. What does heavy forms mean - large data tables? If so, pagination and keyword search can be implemented.

Show original

Translate

Hello
I have extensive experience modernizing legacy business applications and can help migrate your FoxPro accounting system to a scalable, maintainable architecture.

My approach starts with a full analysis of the existing codebase, database, and business processes to identify what should be migrated, optimized, or removed. I will then design the new architecture, including the core/configuration model, database strategy, testing approach, deployment process, and complete technical documentation.

I have strong experience with .NET, desktop applications, database migration, enterprise systems, and long-term maintainability. I can also prepare support, update, and operational documentation to ensure a smooth transition after deployment.

I would be happy to review the current FoxPro project and discuss the best migration strategy.
Da

Hello.

I have been developing desktop and server applications for over 10 years, including C#/C++ and supporting/migrating legacy projects.

First, we need to take a look at what is currently available: the FoxPro source code, the working version of the program, the database structure, modules, work scenarios, and dependencies. The scope can vary significantly depending on how much the code is linked to the database, forms, reports, and third-party components.

Show original

Translate