Applies To
	Product(s):	MicroStation
	Version(s):	V8
	Environment:	N/A
	Area:	N/A
	Subarea:	N/A
	Original Author:	Tim Hickman, Technical Support Group

For those organizations that still haven't moved from MicroStation to MicroStation V8, but are planning to, there is a good bit to consider. The format is very different than any previous versions of MicroStation; in fact it is the only significant format change in Bentley history.

Now in its second version as MicroStation V8 2004, this format includes many dramatically improved capabilities over the original MicroStation format. To reap the benefits, however, users must meet the challenge of moving pre-V8 data into the V8 format. This is where the CAD manager must make some important decisions: Do I do it myself? Do I hire an outside source? What is involved in such a task?

It is the CAD manager's task to set up an environment where the users will be able to work efficiently, determining the best possible workflow for the company. Without proper planning, tools that could enhance productivity will become cumbersome and ultimately useless for the user.

There is no standard checklist for a migration to MicroStation V8 because MicroStation is not used the same way in every company, site, or discipline. With careful analysis and planning, you can build a customized strategy specifically for your organization's needs.

Building Your Migration Plan

The first step: Look at all the data you use on a daily basis. This is the same data you will need to move into the new format. If you were to take everything you needed for your CAD data and put it in a folder for a client, to backup, or to move to a new server on your network, that is the very same data that you want to move to the MicroStation V8 file format.

With a clear understanding of your data, you can begin building your migration strategy. Asking key questions is the best way to begin.

How are you currently using MicroStation?

• How much data on your network is being shared? Or is your organization a one-person shop?
• Do you have custom workspaces?
• Are you using any third-party software (Bentley or other)?
• Where are your design files, cell libraries, custom line styles and fonts?
• Do you have any custom programming for MicroStation (MDL, MACROS, JAVA, etc...)?

If you don't know the answers to these questions, you will need to investigate and find out.

Incorporating the New Functionality

Getting your data over to the new format is only half the battle. You'll want to start using some of the new functionality in the MicroStation V8, which may affect the way you currently manage your CAD department. MicroStation V8 has a lot more to offer the CAD manager when it comes to controlling company standards, including:

• Unlimited levels
• A much larger cell and file size
• Models
• Dimension styles
• Text styles
• The ability to use ACAD fonts and Windows fonts\
• Live nesting for references
• Direct editing of the DWG format
• and much more

You'll need to sit down and figure out how the MicroStation V8 format is going to be used. While this advice might sound simplistic, you have many more options to consider now. You now have unlimited levels, you can work on pre-V8 files, and you can also work on DWG files directly. It is up to the CAD manager to determine how this data is accessed. Will everything remain in its current format, or will we upgrade to MicroStation V8? Does the company deliver a final project in V7-DGN, V8-DGN, or DWG?

Ask yourself these questions:

• Am I currently using SelectServer for licensing? Or are my machines running local node locked licenses?
• Where are my design files?
• Are my users going to work with V8 files only? Are my users also going to be working with pre-V8 and DWG files?
• Do I currently use a level naming convention?
• What kind of company-wide level naming will be used? And how will this be enforced (seed files, attached levels, OR using a DGNLIB file)?
• What fonts are currently used? Do I continue to work this way or do I allow the use of Windows and ACAD fonts? What about TextStyles?
• Along the same lines if TextStyles, what about DimensionStyles?
• Is this the time for consolidating and standardizing our cell libraries?
• A new set of seed files? You may want to look into sheet files also.
• Custom programming (MDL, MACROS, etc.) may need to be re-compiled or re-written.

Beginning the Migration - One Project at a Time

If you have a lot of data and many projects that need upgrading, it will be best to do your migration a little at a time, rather than all in one big step (perhaps doing one project at a time, starting with the smaller ones first). By doing it one project at a time, you will give yourself a chance to find anything you may have missed or forgot to cover (using sheet files and models as compared to your current referencing of files, for example).

Working in your favor is the MicroStation V8 directory structure, which is almost identical to that of MicroStation/J. If you have a custom workspace in place, you can most likely use it with MicroStation V8. The new format uses the existing configuration variables, along with new variables that allow more functionality and control. However, the pre-V8 user preference file (*upf) cannot be used in the MicroStation V8 workspace.

If you have been using MicroStation right out of the box, un-modified, your migration to the MicroStation V8 format will be a lot easier than that of someone who has customized MicroStation.

Ask yourself the following for each project:

• Will we convert all these design files to V8?
• Will we convert all these cell libraries to V8?
• Will any new projects be done in the new V8 format?
• Will any files received from clients, vendors, contractors, or others be converted to the MicroStation V8 format?
• Will a standard level naming convention be put in place and enforced through a DGNLIB reference?
• Will there be a standard set of TextStyles used and will they be enforced through a DGNLIB reference?
• Will there be a standard set of DimensionStyles and will they be enforced through a DGNLIB reference?
• Can my custom programs be re-compiled (MDL) for the MicroStation V8 format?
• Who wrote the custom MDL, MACRO, JAVA, etc...? Do I have the code?
• Do new seed files need to be created?
• Will sheet files and models be used?
• Will I need to update users with the new processes for levels, textstyles, dimensionstyles, and so forth?

Educating the Users

Educating your users on MicroStation V8 is the best way save time while migrating. Provide them with a new workflow and good set of reference materials in addition to training.

Avoid Common Problem Areas

The following questions will help you avoid common problem areas during migration:

• Hardware: What are the new hardware requirements? Do we need upgrades?
• Software: How will the new software be deployed and licensed?
• Data: How will the existing data be backed up and upgraded?
• People: Are users trained and ready to use the new software?
• Customizations: How are we going to migrate company specific customizations (custom GUI, workspace CFGs, plotting scripts etc.)?
• Applications and Utilities: Do my third party applications work correctly? How about custom applications we authored?
• The number one thing to remember when migrating this data: BACKUP, BACKUP, BACKUP!

Further resources:

The Bentley Institute offers training for migrating to MicroStation V8.

Bentley Professional Services can assist your organization in making the change to MicroStation V8