Posted by David Kuketz on March 3, 2020
Posted by Utopia Marketing on July 15, 2019
There can be a lot of risk when migrating to a new platform like SAP S/4HANA. How do you ensure you're creating a smarter approach to managing the data up front?
It’s time to face the reality... no more kicking it down the road... your organization just might have a data problem. Maybe it started with a few processes that broke down over time. Maybe someone left and took with them the knowledge of their homegrown data archiving strategy. Maybe manual entry or data manipulation destroyed the integrity of your change management. Regardless of how it happened, it has likely led to some enterprise-wide bad data habits.
A major step on the road to system modernization is the migration to a unified platform, in this case... SAP S/4HANA. While enterprises are prepared to invest in SAP S/4HANA, it’s critical to realize that you need to first invest in your data. You can have the nicest garbage can on the block, but the inside is still trash.
Posted by Katie Mowery on March 30, 2018
When you’re migrating from a non-SAP legacy system or from an SAP ERP system and implementing SAP S/4HANA, your master and transactional data must be migrated from the legacy system into a new environment – and with that comes a lot of things to consider, plan for and build processes around.
Data migration is one of the biggest risks to a new system implementation. 38% of data migrations fail due to a lack of understanding of the source and target systems and poor planning/execution by project teams. A failed data migration as a part of your SAP S/4HANA implementation means decreased value of the powerful business platform because it’s only as good as the data enabling it.
SAP® S/4HANA enables organizations to lower their operating IT costs by simplifying their IT landscape. However, every organization has different needs. Implementing a data management strategy is imperative for organizations to accelerate their movement to SAP S/4HANA in a cost-effective manner.
We’ve seen it before. A company makes a big investment in a new ERP system, and a BI system, then added Balanced Score Cards and very pretty dashboards. But the CEO still gets reports in an Excel spreadsheet. Ever wonder why this happens? There are many reasons, however a common one is that when the new system was implemented, no one cleaned the data from the old system(s) BEFORE it was loaded into the new system.
As a result, all the reports that had wrong information before – still have wrong information. They just now have eye catching buttons and dials on them!
This happens time and time again because the data migration/conversion stream of the ERP system project did not receive the attention that it deserved. It was left to another team, another stakeholder, another phase maybe– you know the old story. "Here is the file format we need – provide the data in this format and we’ll load it for you." But the responsibility for the quality of the data is with someone else.
Posted by Jeff Knotts on November 28, 2017
Since SAP S/4HANA is the latest and greatest technology from SAP many people may find themselves asking this question. It’s the same question you may ask after a rollout of any new business suite or enterprise-wide system.
Posted by Utopia Marketing on April 1, 2014
Data migration guru, John Morris, wrote “data migration is a business issue and not a technical issue.” Having been through many data migration projects myself, I couldn’t agree more. When choosing a framework for data migration one has to keep this in mind. Furthermore when it comes to migrating data into SAP, one needs to take into consideration a few other truisms, such as:
Posted by Utopia Marketing on July 31, 2012
If you’ve conducted a data migration, or you’re about to do one, you can expect—at somewhere, some point in that project—to hear one of these nine different statements: