AM/FM/GIS Migration: A Formula for Success
Challenges of Migration
The decision to migrate poses many challenges from selecting the system, to building the software and
applications while maintaining functionality and data integrity. The key element in a migration implementation
strategy is to” do your homework” first. That is, before starting the project, identify the overall corporate needs
and review possible solutions. The following areas require investigation and decision before proceeding:
System
In reviewing and identifying system selections, companies are faced with the decision to stay with the
same vendor and move to newer technology or select a new vendor. Either way the decision poses
challenges and opportunities for the organization. Some of these challenges are:
Software
The following are options for software and applications development:
- Migrate existing applications
- Migrate existing applications and develop new applications
- Design and develop all new software and applications
Other system and software selections to be made are:
- Operating System
- Database Management Systems
- Communications
- Graphical User Interfaces
Data
Efficient and effective data retrieval is the primary reason for upgrading to a new computer system.
Companies want better and faster ways of accessing their information. The new technology is often so
exciting that it is easy to concentrate on the computer system for its own sake, rather than focusing on
how this new system accesses data in a way that is beneficial to the information needs and work processes
of the company. The fact that we are talking about replacing hardware and software and not data, proves
that data is the real value. As a result the most important task of data migration is ensuring that the data
is translated from the old system to the new system intact. There are usually several types of software
programs written to ensure data integrity before, during and after migration has occurred. It is extremely
important that the data accuracy is maintained throughout the migration processes.
Migration usually takes from several weeks to several months to accomplish, depending on the amount of
data to be processed and is accompanied by several issues. For example, how long will the migration
take? During this “down time” should data be frozen? Should backlogged work be migrated and posted
separately? Companies must analyze their work processes and the amount of time it takes to migrate
data before determining how to migrate the bulk of the data and maintain the data in the new system.
One way to accomplish this more smoothly is to perform a small pilot migration.
Resource
It seems the next logical question is who should do the migration. Some companies have elected to do the
entire migration in-house, while others have contracted the system vendor to migrate the applications and
data. Another option is to hire a consultant or conversion vendor to do it or assist. The following are
some reasons why you may select
In-house migration;
- Most familiar with software, data, applications
- Easily controlled schedules
- No external costs
System Vendor;
- Knows hardware and software platform
- Contact for “complete” solution - single source accountability
- Maybe faster/ have more ready resources
Consultant/Conversion vendor;
- Understanding of multiple systems
- Familiar with data issues, and perhaps your data
- Maybe faster/ have more ready resources
Migration Plan/Strategy
Once you have evaluated the benefits, considered the challenges, made a decision about which system to migrate
to, determined who will be involved in helping you get there, what data will be included or not included, and
how long the migration process will take, there remains one more critical element of your migration plan that stiU
needs to be addressed. Just as executive management support and user acceptance were essential to the success
of your initial conversion project, so they will be for migration. Engaging the support of these two groups must
not be left to chance.
Manage Corporate Expectations / User Acceptance
Controlling management expectations and user acceptance while maintaining focus on the migration project can
be the most difficult challenge a project team can have. During the justification process a level of expectation has
been set and it is the project team’s responsibility to maintain a high level of confidence throughout the migration
project. While the project team can not control all aspects of the migration, an implementation procedure which
includes clearly defined and articulated goals, regular fact-based progress updates and good training can create
an environment of “invested users and managers with real world expectations.
The project team must develop a firm strategy for working with potential users, and shape their project
expectations long before actually meeting with users. This strategy should focus on defining current and future
users because the questions/ requirements for these two groups will be dramatically different. The table below
highlights some of these differences.
Conclusion
Given the rapid advance of technology, systems that come and go, and a competitive market pushing utilities to
ever greater efficiencies and cost containment, some form of migration is an inevitability for all utilities. With an
approach based on sound business principles and practices, logical decisions and a vision for the future,
migration can be the pathway to successfully providing services in tomorrow’s market place.
