Introducing Top 5 Factors To Consider For BOBJ Migration

Jim Sun

Business Objects was first introduced in 1994 as a reporting tool. The company was acquired by SAP in 2007 and has become one of the main reporting platforms in the market. In the latest BI 4.1 release, many functions have been enhanced with the aim of simplifying the tools and the platform and enhancing the user experience. More and more clients are considering migrating their BO system to a newer version, but when considering migrating your BI system, what are the key factors to consider and what are the possible obstacles in the project? You will find the answers from this blog post

  • Training. There is nothing more important than getting your people to accept the change, especially for a reporting system such as Business Objects. Not only the changes, but also the technology. The developers and administrators may not be familiar with the interface and use of new client tools, and also the end-users and non-technical employees may be reluctant to learn the new techniques. Training for end-users and internal employees is quite important to prepare for a succesful implementation.
  • Content. Every migration project could be a report/universe cleansing project. You do not want to spend 3 months to migrate those useless reports/universes into your new BI system. You need to be selective of the content to migrate. For example, if the key features you are using in Dashboard Designer are still the same as those in the new version, then it makes no sense to install the client tool into your new system. It could be a waste of time doing so.
  • Licensing: The license management on the latest BI system from SAP will be auditted by SAP by a new utility named Business Objects License Management Tool, so basically, if you are not planning to buy all the licenses inside of BI 4.0 as an example, then you had better decide how many users can use each kind of feature before proceding with the migration.
  • Reports: There are some documents that may be used in previous versions but not used in the latest version. For example, .unv files are universes that were developed in UDT in BI 3.0 or earlier versions but are not widely used in BI 4.0 and later versions, IDT is a new universe development tool in the latest versions. And Desktop Intelligence will no longer be used in any further versions after BI 4.0. So the client needs to select how to use and migrate those legacy documents/universes from either repository or local folders.
  • Support: If you do not want to lose support from your software vendor, which is SAP, you had better schedule your upgrade soon. Basically, any version that is prior to BOBJ XI3.2 SP2 is not supported by SAP anymore. Version XI 3.3 SP3 will not be supported after 12/31/2015, which means that if you want to get official support from SAP, it is better you migrate your BI system to a newer one if you are using BOBJ XI 3.3 SP3 or earlier version.

BOBJ migration

System migration is not simply "copy and paste" what you have in your system to the targeted system; the clients need to be very careful to prepare and implement the project to ensure a successful migration. We provide professional diagnostics of BOBJ/BW/HANA environments and migration plans and strategies. Click the button below to read a case study of a BOBJ migration project led by ATCG Solutions.

Have you ever read a blog and wanted to bookmark it but forgot? Or maybe you're like a lot of people and tend to keep dozens of windows open, only to experience a crash or otherwise lose track of what you were doing? Simple solution is to print this out, and that is why we provide a PDF version for later use, which you can get by pressing the button below.