We have a current application that's fairly well established, but we're adding new products and tools and consolidating everything under a new brand. This new brand will sit under a new site domain, but all the old content is relevant and useful.
We already have a domain ready, but we aren't sure what the consequences would be for some of our proposed methods and wondered if anyone here has any experience with this?
I'll list some of the options we have on the board atm:
- Move the old site into a sub-folder of the new domain, e.g. newsite(.)com/oldsite
- Permanent redirect to from old domain to new (but then we'd lose all the old blog posts, etc.)
- Leave the old site in place, but replace the home page with CTA for users to go to the new site.
- Copy over all content to new site and use 301 directs from all older pages to all new duplicated ones.
The thing is, users for the current application will still need to be able to log into their account. We aren't erasing the whole application or user base, but we do want to wind down the number of users creating new accounts. These should be directed to the new domain.
I also don't want to have a negative impact on the new domain scores in anyway. I know there's a lot going on here, but can anyone recommend anything?