Migration


Life Cycle
The Linux Box team has years of experience migrating, porting and converting systems.

Call us at (734) 761-4689 so that your port, migration, or conversion does not come with any surprises.

Decide

Choosing to migrate from one system to another is no trivial matter. It needs to be done only when necessary and not in order to follow the current trend otherwise there is no gain.
The gain can be in the form of:
  • Improved or added functionality (identify, list & document)
  • Reduced cost (identify expectations and starting point)
  • Increased productivity (measure and document current productivity)
  • Contractual obligation (document impact of delays)
  • Standardization and architectural coherence (document requirements)
Helpful Hint: Verify your information and separate the facts from the anecdotes

Plan

Whatever the reason, a migration to a new system must be planned carefully. The plan must have at least the following line items:
  • Identify a reasonable number of options
  • Evaluate the options and
  • Select the optimal option based on:
    • Gap analysis
    • Cost benefit analysis
    • Constraint analysis
  • Specify data conversion requirements
  • Develop a rigorous testing and validation plan
  • Develop a training program for the use of the new system
    • Technical staff
    • End Users
  • Develop a conversion plan A
  • Develop a conversion plan B
  • Implement a problem management & Enhancement Request system
  • Implement a change management system
Helpful hint: Watch out for scope creep

Execute

  • Execute the plan
  • Document exception
  • Monitor results
  • Celebrate and reward
Helpful Hint: Throughout the process: communicate, communicate, communicate

Measure

Track actual results against planned expectations
  • Did functionality increase / improve
  • Are the costs reduced? by how much? how soon?
  • Did Productivity increase
  • Were contractual obligations met on time or were there penalties involved?
  • Does the system adhere to company standards and architectural design
Helpful Hint: Have all the "before" data completed in the planning phase, and have a plan of what to do if the measurements vary, positively or negatively, from expectations.

Monitor & Follow up

  • Problem & Enhancements Management system
    • Review reported exceptions
    • Assess relevance and cost to repair
    • Prioritize corrections
    • Schedule corrections
    • Implement: code, test, validate, install using the Change Management System
  • Implement permanent solutions to any temporary conversion workaround
  • Monitor performance
  • Correct deficiencies
  • Plan and implement enhancements and improvements
Helpful Hint: Just because something is on a request for change does not mean it's really necessary. Follow the assessment process with each request.