A rebuild is not automatically the best answer when a website becomes dated or difficult to use.
The first question should be whether the current structure can still support the experience the business needs.
Repair is often appropriate when the core platform remains sound but navigation, mobile behaviour, content hierarchy, forms, performance or visual presentation have fallen behind.
A rebuild becomes more reasonable when the underlying architecture prevents important customer journeys, creates persistent technical limitations, cannot be maintained safely or makes necessary integrations impractical.
The useful decision is therefore not “old website versus new website”. It is:
What is preventing the current website from representing the business and helping the customer complete the right action?
Swarajya's approach is to preserve functioning parts and replace only what materially limits the required experience.