Inventory the hosted features customers rely on
List pages, forms, booking flows, member access and other connected services that actually exist in your setup. Check the current account and plan rather than relying on a generic export assumption. Content recovery, design reconstruction and functional replacement are separate tasks. Ask the new supplier to explain which of those tasks their proposal includes.
Verify addresses and operating tasks
Decide which existing URLs should stay and map genuinely changed addresses to relevant destinations. Then consider the editor: how will staff update a service, manage a booking or receive an enquiry after the move? A static Astro site can serve public content, while transactional functions may need separate services. Do not promise that every hosted feature transfers unchanged.
A practical check before you buy
Recreate one important service page and its contact journey in a controlled preview. Compare content, mobile behaviour, URL handling and receipt at the intended destination before extending the rebuild.
| Decision | What to consider | What to check |
|---|---|---|
| Content | Text and original media | Inspect retrievable material |
| Functions | Forms and connected services | Test the replacement journey |
| Addresses | Current public URL list | Check retained and changed paths |
An illustrative business scenario
A UK training company should inventory any booking and course-management functions separately from the visible course descriptions.
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.