Adobe Business Catalyst: Planning A Replacement Website

Replacing a legacy website means recovering the content and functions the business still needs, then choosing a maintainable way to deliver them. An old Adobe Business Catalyst review is not a suitable specification for a new project.

Inventory The Site Before Choosing A Platform

List the pages, files, forms, product information and administrative tasks still in use. Separate a feature someone relies on from a feature that merely exists. Identify who controls the domain and where backups or exports are stored. Do not assume an old account still provides a recoverable copy.

Design Around The Current Workload

A small informational website may need only a simple publishing process. A property catalogue or customer portal needs structured data and clear permissions. Choose the approach after defining those requirements. Ask how content can be exported and what happens if you change supplier later.

Preserve Useful URLs And Content

Record existing addresses and map each important page to its closest replacement. Keep relevant text, images and downloadable files where you have the right to use them. A rebuild should improve the answers people find rather than send every old address to the homepage.

Test The Replacement Before Switching

Check forms, confirmation messages, search, content editing and mobile navigation. Confirm the backup and recovery process. Agree a launch checklist and rollback plan, then monitor the important journeys after the move. The end result should be a maintainable website with responsibilities that are easy to understand.