Why, may I ask, are you moving rather than upgrading?
We are moving because our organization has an internal Jive site as well as an external one that we can use to collaborate with people who do not work for us.
Some pretty big questions here. Can we narrow the field a little with some clarifying questions?
- Sounds like we have 2 jive instances. A new one (what version) and an old one (what version). One is internal only and the other is external facing correct?
- I'm assuming the migration you're talking about is to the external instance then, and you're hoping to provide some added privacy for these internal users there.
- How complex is the structure for each of these communities (number of groups, number of space levels)
- What's the rough order size in users, pieces of content
- Do we have customizations of any kind in either of these environments? Do we expect that our migrating users are going to lose any functionality?
I have a good amount of experience doing these, from just upgrades, to combining several communities into one and re-purposing single communities for a larger purpose.
A much different prospect if we're talking a couple hundred users versus a couple of thousand.
Could you not bridge the two communities, rather than starting afresh (which I assume is what you're doing) or use a CNAME record in your DNS to transparently redirect your users to the new community?