Enterprise Migration Challenges – .NET Framework 4.8 to .NET 8 Using Cursor AI

Support Help
, , , ,
1

Hello Cursor Team,

I am currently using Cursor AI (Enterprise License) to migrate a large-scale .NET Framework 4.8 application to .NET 8, including integrations with Azure services, EF Core, and Clean Architecture patterns.

While Cursor AI has been helpful, we are encountering several challenges during enterprise-level modernization.

Issues Observed

  • Inconsistent migration results, particularly for complex endpoints

  • Missing or partially migrated DTOs, models, and dependent services

  • Incorrect or incomplete Entity Framework → EF Core conversions

  • No detection or warnings for circular dependencies

  • Partial or sometimes irrelevant code generation

  • Performance degradation when handling large prompts or multi-file refactoring

  • Limited architectural awareness for layered / Clean Architecture solutions

  • Occasional instability during large-scale code changes

Clarifications Requested

I would appreciate guidance on the following:

  • Best practices when using Cursor AI for large enterprise codebases

  • Recommended workflow for dependency-aware migrations

  • Official guidance for EF Framework → EF Core migration

  • Planned improvements around performance and multi-file context awareness

I would greatly appreciate any recommendations, roadmap insights, or enterprise best practices you can share.

4

Hi @Fayaz and thank you for your post.

While I myself do not work with .NET I would recommend following based on my experience:

  • Your Cursor Enterprise contact may have more info on large refactoring and best practices to set up.
  • Use Skills (Rules) & Subagents to better guide AI towards doing the right things.
  • Check with your framework developers if they have clear migration steps, incl. Skills as I have seen many frameworks provide this already out of the box. Many frameworks even have scripts that migrate codebases automatically.
  • Break down the tasks into manageable parts and in right order of dependencies and required changes for your framework
  • Include scripts into Skills that run dependency and similar checks
  • Ensure that you have sufficient tests to cover use cases of the codebase and ask agent to test
  • Always let the agent discover files rather than attaching them.

Some level of instability is expected on large codebase migrations as not all files can be updated at once.

More resources we have:

Looking also for more .NET experienced developers in the community to chime in.