Cost of moving from Access to .Net

Question

My company has a fairly complicated Microsoft Access Front End and a SQL Server Back End application which is mission critical to our operations. Since Microsoft has not provided any support to Access for sometime, the higher-ups are getting anxious about the viability of the application in the future. We are thinking about moving from Access Front End to .Net architecture. My question is: what is (the rule of thumb of) the cost involved migrating from Access Front End to .Net architecture? I really appreciate it if you can give me some idea when it comes to the size and the complexities of your organization and your experience migrating to .Net architecture.

Answer 1

Hi @ming kwei ,Welcome to Microsoft Q&A. When migrating from a Microsoft Access front end to a .NET architecture, costs vary depending on the size of the organization and the complexity of the application. I'm only showing a partial view, you may need to consult more professional personnel.

1. Application complexity: The complexity of the current Access front-end application is an important factor in estimating the migration cost. Migration can be more complex and expensive if the application has a large number of forms, reports, macros, and complex business logic. Also, if the Access application is tightly integrated with other Microsoft Office products or third-party applications, migration may require additional resources and time.
2. Data Migration: Migrating from an Access application's SQL Server backend to a .NET architecture can require careful planning and execution. Data schemas, relationships, and data types in .NET may differ from Access, so data conversion and validation may be required during migration. The complexity of the data and the volume of data being migrated affects the cost of the migration.
3. User interface and user experience: Migrating from an Access front end to the .NET architecture may involve redesigning the user interface and user experience of the application. This may include creating new user interfaces using modern web technologies or desktop frameworks, which may require additional development effort and cost.
4. Business logic and integration: If an Access application has complex business logic, workflow, or integration with other systems, recreating or refactoring these components in .NET may require additional work. This might include rewriting custom code, developing new APIs, or integrating with different third-party libraries or services.
5. Testing and Quality Assurance: Migrating to a new architecture requires comprehensive testing and quality assurance to ensure that the migrated application is functional, secure and meets the organization's requirements. The cost of testing and quality assurance activities should be considered in the total cost estimate.
6. Skills and resources: The availability and skill sets of internal resources within the organization, or whether external specialists need to be hired to perform the migration, will affect cost. .NET is a different technology stack than Access, so your team may need to acquire new skills or hire someone with .NET expertise.
7. Timeline and project management: The timeline of the migration project and the project management methodology adopted by the organization will also affect the cost. Longer timelines may require additional resources, resulting in higher costs

Best Regards,

Jiale

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.