Keep SQL, replace coupling
Stored procedures stay in service for phase 1, but the PHP page sprawl is replaced with typed API contracts and modular frontend routes.
TransPress Next
Rebuilding the transport platform on a modern, typed stack without replacing the SQL core.
The legacy PHP system is feature-rich, but it is tightly coupled, hard to extend, and risky to evolve. This new workspace keeps SQL Server in place while introducing a modern frontend, a typed API, and a cleaner path for future features.
Modernization goals
What changes first
Turn legacy screens into product modules
Orders, invoices, fleet, customers, finance, and trip operations become coherent product surfaces instead of dozens of loosely connected PHP files.
Make future features cheaper
Once auth, data fetching, and permissions are centralized, new capabilities can be added without copying business logic across pages.
Legacy scope
Business modules already identified
Operations
OrdersInvoicesLive TripsTrailer Status
Fleet
TrucksTrailersDriversEmployeesTruck Driver Link
Commercial
CustomersCreditorsProducts
Pricing
Standard RatesCustomer RatesLocation RatesDriver CommissionDriver Trip Commissions
Finance
PaymentsReceived PaymentsPending PaymentsBalance SheetBusiness FinancesFund StatusManage AccountsManage FundsExpenseGeneral Expense
Trip Setup
LocationsTrip Expense TypeMaintenance Expense TypeMaintenance Expense
Admin
Manage BusinessManage GroupsUser ManagementUser SupportSystem SettingsGenerate BackupDubai TradeRoadmap
Execution path
Incremental migration phases
Phase 1
Compatibility foundation
Mirror legacy login, permissions, and dashboard procedures behind a typed TypeScript API.
Legacy password hashing bridgeSession-safe auth responseDashboard overview adapter
Phase 2
Operational slice
Port Orders and Invoices first because they anchor dispatch, billing, and customer communication.
Order list and detail workspaceInvoice workflowSearch and filtering primitives
Phase 3
Master data migration
Move customers, drivers, creditors, trucks, trailers, and rate management into the new UI.
Reusable CRUD patternsValidation rulesAudit-ready edit flows
Phase 4
Feature expansion
Once daily operations are stable on the new stack, add mobile-friendly and customer-facing experiences.
Real-time trip boardCustomer portalApproval workflows
After migration
Feature runway unlocked by the new stack
Dispatch Command Center
A single view for live trips, assigned drivers, delayed legs, and proof-of-delivery events.
Customer Workspace
Shared access for invoices, shipment visibility, statements, and downloadable documents.
Exception Automation
Notify teams when unpaid invoices age out, maintenance is overdue, or trip costs cross thresholds.
Analytics Layer
Operational KPIs built on typed API responses instead of handcrafted page scripts.