Inventory before integration
We start with domains, access owners, editing tools and existing integrations. I record each site’s audience, purpose and dependencies, then propose what is worth combining. Similar looks alone are not a reason for two websites to share a database.
One source for shared information
A central contact can be managed in one place and appear in several different interfaces. A brand-specific service description remains local. The content model therefore distinguishes shared, local and inherited values, including what happens when a local field is empty.
- Shared fields and their owner
- Local edits that leave other sites untouched
- Explicit inheritance rules
- A preview of every affected website
Identity stays independent
Typography, navigation, presentation and content rhythm can be entirely different. A shared technical foundation does not require a shared appearance. Each brand gets a structure suited to its purpose, with an underlying system that can be maintained.
Content has an owner
Before publication, we decide together which website owns each topic. Copying identical sales pages across domains does not create a new reason to visit. Each brand receives content for its audience; necessary duplicates receive deliberate search and canonical handling.
Connect without a single large cutover
Migration proceeds by website and data type. Trial transfers uncover mismatched fields, missing files and old links before visitors are moved. Domains, business email and applications are treated separately so a public website change does not interrupt other services.