One temptation of developers is to rewrite an entire codebase. There are pros and cons for you to decide, and yes, it is often harder to read existing code than it is to write new code; but please do bear in mind that rewrites take time and can be hugely costly for your business.
Always bear in mind that the sum of your technical debt from any one project can never be greater than starting the project from scratch.
Maiz Lulkin wrote the following in a brilliant blog post:
"The problem of big rewrites is that they are a technical solution to a cultural problem."
Big rewrites are horribly inefficient, especially when you simply cannot guarantee that developers will know any better now. Architecting the new system and migrating the data inside the deadlines can be a tall order.
In addition to this, deploying the big rewrite can be hugely problematic; deploying such a change to the entire codebase of an application can be lethal. Try to deploy code regularly in frequent intervals...