ASP.NET Core Site Migration
Budget: $30 – $250 USD
I am moving an existing ASP.NET Core website to a new environment and need an experienced developer to oversee the entire migration alongside our in-house server team. The site relies heavily on custom User Authentication and Content Management modules, all tied to a SQL Server back end, so absolute continuity is critical.
You will first review the current solution, map every dependency (NuGet packages, third-party libraries, static assets), and replicate the build on the target server. From there, I’ll need you to:
• Migrate and restore the SQL Server database, updating connection strings and any environment-specific settings.
• Re-deploy and configure the User Authentication and Content Management modules so they compile, run, and pass functional testing on the new host.
• Work directly with our IT staff to adjust firewall rules, IIS/Kestrel settings, and SSL certificates where required.
• Run end-to-end tests to confirm login flows, role permissions, and content editing/publishing all behave exactly as before.
• Hand over concise deployment notes so future releases follow the same steps without surprises.
Acceptance will be based on zero downtime during cut-over, successful smoke tests of every authentication path, and verified content edits in production. If you are comfortable handling ASP.NET Core pipelines, SQL Server migration scripts, and real-time coordination with ops engineers, I’m ready to get started right away.
You will first review the current solution, map every dependency (NuGet packages, third-party libraries, static assets), and replicate the build on the target server. From there, I’ll need you to:
• Migrate and restore the SQL Server database, updating connection strings and any environment-specific settings.
• Re-deploy and configure the User Authentication and Content Management modules so they compile, run, and pass functional testing on the new host.
• Work directly with our IT staff to adjust firewall rules, IIS/Kestrel settings, and SSL certificates where required.
• Run end-to-end tests to confirm login flows, role permissions, and content editing/publishing all behave exactly as before.
• Hand over concise deployment notes so future releases follow the same steps without surprises.
Acceptance will be based on zero downtime during cut-over, successful smoke tests of every authentication path, and verified content edits in production. If you are comfortable handling ASP.NET Core pipelines, SQL Server migration scripts, and real-time coordination with ops engineers, I’m ready to get started right away.