converting V8i Workspace to Connect

The way configuration is organized between V8i and ORD/Connect has changed significantly. Here's an article about considerations that should be made.

Another explaining how the configuration has changed:https://communities.bentley.com/products/microstation/w/microstation__wiki/24186/what-configuration-changes-have-been-made-in-microstation-connect-edition

A series of articles: https://communities.bentley.com/other/old_site_member_blogs/peer_blogs/b/marc_thomass_blog/posts/connect-edition---custom-configuration---part-1-initial-creation-steps

And a whole collection of blogs: https://communities.bentley.com/products/microstation/b/microstation_blog/posts/configuration-blogs-toc

There's a lot more to it, including the fact that ORD files need to be "branded" to a particular workspace/workset combination.

I would SERIOUSLY suggest talking to the powers that be, and convincing them to keep V8i work in V8i, and start fresh projects in ORD. While it may be possible to view the files in one or the other, it is NOT possible to do any work across versions. Matter of fact, there are certain versions of ORD that aren't even compatible.

There's an entire forum dedicated to Product Administration. While ORD has some specialized requirements, much of the plain MicroStation information is valid.

There are many settings in CONNECT that are different from values that many offices used in V8i. Some of these might be optional, but others seem to be required. We tried making our ORD workspace an evolution of our V8i workspace. We are now having to create a new workspace using the "recommended" settings in order to make sure everything works properly. The original ORD workspace might permit a migration, but we will consider that workspace a temporary kludge. 

There are many settings in CONNECT that are different from values that many offices used in V8i. Some of these might be optional, but others seem to be required. We tried making our ORD workspace an evolution of our V8i workspace. We are now having to create a new workspace using the "recommended" settings in order to make sure everything works properly. The original ORD workspace might permit a migration, but we will consider that workspace a temporary kludge.