Preserve what customers and editors already use
List useful text, original images, working URLs and genuine inquiry patterns. Check which pages attract relevant visits or answer recurring sales questions, using the data available rather than intuition alone. Keep an independent copy of content you own before changing access. The old visual layout may be disposable while its wording, addresses and workflow knowledge remain valuable.
Separate a visual rebuild from a platform decision
A new supplier may need to recreate layouts without discarding the underlying content. Some functions depend on the existing platform and require separate replacement. Ask how each important function will work in the new setup and who maintains it. Avoid both extremes: copying every old weakness or starting again without understanding why particular pages and links matter.
A practical check before you buy
Choose one useful page and one inquiry route. Trace their content, URL, assets and delivery destination, then ask the supplier to classify each item as retained, rewritten, rebuilt or retired.
| Decision | What to consider | What to check |
|---|---|---|
| Useful content | Verify and retain | Confirm ownership and accuracy |
| Existing addresses | Review before changing | Plan relevant destinations |
| Platform features | Identify dependencies | Specify replacement behavior |
An illustrative business scenario
A US contractor may keep useful project photos and service URLs while rebuilding an inquiry route that currently depends on a personal account.
This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.
Discuss the right scope with ImbaHub
ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.