The primary goal is to achieve 1:1 functional parity with the existing application Codeigniter 2.0 (Mysql4.6), preserving all business logic while completely re-architecting the codebase for security, performance, and maintainability. ● In-Scope: Full migration of all business domains, database layer migration to Eloquent, API refactoring, new authentication system, and implementation of automated tests. ● Out-of-Scope (Initial Phase): Major UI/UX redesign (will use Blade/Alpine.js), new feature development, and database schema normalization (will use the existing schema as-is). Target Technology Stack ● Framework: Laravel (latest stable version) ● Language: PHP 8.2+ ● Database: MySQL 8.0+ (using the existing stoma_ prefixed schema) ● ORM: Laravel Eloquent ● API: Laravel API Routes with Sanctum for authentication. ● Frontend: Blade templates with Alpine.js or vanilla JavaScript. ● Local Development: Docker via Laravel Sail. ● Testing: Pest / PHPUnit. The first part of our CodeIgniter 2.0 application is already converted onour new Laravel application everything else is still waiting to be converted in the old framework. I need you to dive into the existing repo, study the finished Laravel section, and carry that same structure and style through the rest of the codebase so the whole product runs on Laravel + MySQL end-to-end. You can follow standard Laravel best practices—service container, Eloquent, queues, policies, and proper environment separation—no additional house style guide will get in your way. Here’s how I see the work: • Audit what’s in our CodeIgniter and convert over to our new Laravel application. • Incrementally port controllers, models, and views, replacing legacy queries with Eloquent where sensible. • Keep the existing MySQL schema unless refactoring clearly improves performance or maintainability. • Ensure every controller, model, and query is compatible with PHP 8.x, maintaining current business logic and database schema. • Audit the existing PHP codebase, flag outdated or deprecated patterns, then refactor or rewrite it in the latest stable Laravel release. • Keep an eye on security practices, performance tuning, and future maintainability while you modernise the code. The deliverable is a fully functional Laravel application that mirrors (and ideally improves) all current features and is ready for production deployment. Deliverables 1. Git commits or pull requests showing the Laravel migration, documented line-by-line where logic changes occur. 4. Deployment guide so our developer can reproduce the build and roll out updates to our live server. If that sounds straightforward to you, let’s get moving—I’ll provide Git access and a quick rundown of the converted module so you can hit the ground running.