text: **3.17 Data migration from a non-virtualized storage subsystem**
  
  Data migration is an important part of a Storwize V7000 implementation. Therefore, you must 
  prepare a detailed data migration plan. You might need to migrate your data for one of the 
  following reasons: 
  
  (cid:2) Redistribute workload within a clustered system across back-end storage subsystems 
  (cid:2) Move workload onto newly installed storage 
  (cid:2) Move workload off old or failing storage, ahead of decommissioning it 
  (cid:2) Move workload to rebalance a changed load pattern 
  (cid:2) Migrate data from an older disk subsystem to Storwize V7000-managed storage 
  (cid:2) Migrate data from one disk subsystem to another disk subsystem 
  
  Because multiple data migration methods are available, choose the method that best fits your 
  environment, operating system platform, type of data, and the application’s service level 
  agreement (SLA). 
  
  Data migration methods can be divided into three classes: 
  
  (cid:2) Based on operating system; for example, using system’s Logical Volume Manager (LVM) 
  (cid:2) Based on specialized data migration software 
  (cid:2) Based on the Storwize V7000 data migration features 