Migration from SAP to JDE 9.1



Hi All,
We have recently upgraded from XE to JDE 9.1.
The system is quite stable and all our BUs (Business Units) are already using 9.1 without any problem.
Now there is a new requirement to migrate one of our new BU from SAP to JDE 9.1.
We would like to understand
1. Is it ok to migrate from SAP to JDE 9.1. (We couldn't find much information from internet whereas lots of information available for JDE to SAP and not other way around)
2. what are the pain points / Challenges / Potential failures especially from data migration point of view.

In case if this is not a good idea, may be we can think of fresh JDE implementation and carry forward the begining balances from SAP.
The reality is that an SAP to JDE migration is no different to any other ERP to JDE migration and what is required to be completed really depends on the alignment of the BU using SAP to the rest of the business that is using JDE. So if you are just consuming the new BU into your existing JDE system then you just need to determine what data is appropriate for them to continue operating after you cut them over. If the alignment doesn't exist then you need to make the decision on whether you make changes to your existing JDE instance that may negatively impact the existing JDE user base or alternatively you fire up a new JDE instance and use that for the BU that is currently running SAP. Any of those options will be significantly cheaper than continuing to operate, support and upgrade both SAP and JDE.

Data migration should be focused on master data, open transactions (there should be as few of these as possible) and balances. Trying to migrate transaction history is where the pain will really kick in. One other method where the open transactions part proves particularly difficult is to do a phased migration where both JDE and SAP are used by the business at the same time. This is generally to be avoided but sometimes it is the lesser of two evils.

You haven't really specified what modules of either JDE or SAP are currently being used and whether it is just SAP ERP or also CRM or SRM as well so it is a bit difficult to judge how difficult a task you're looking at.
Thanks Russel. I am getting better clarity from your reply.
• Aligning the new BU to the rest of the business should be possible as the Business processes are similar.
• Currently we are not thinking of another JDE instance for the new BU. Maintenance and Change management will be troublesome otherwise.
• We are thinking to store the selective transaction history (SAP Data) as such (Without migrating) into an isolated database for ready reference, in case if the business needs this information for auditing purposes. We may have to provision them with some inquiry tools.
• Migrating the open transactions is the nightmare now. JDE-SAP coexistence sounds equally scary. This is the area we will be exploring. Somehow we need to do the cutover with minimum downtime without interrupting the business much. (During our upgrade the downtime was almost Nil as all the cutovers happened during weekends)
• The New SAP BU is using Finance, Procurement and inventory. I also do not have much information about the new BU. Will get to know soon.
I found (in multiple migrations from SAP to JDE) that the real pain is, as Russell says, migrating historical data and transactions. Very few functional SAP resources know where the data is and what the table relationships are. And the technical resources have usually no idea about what the data is for and how it relates to business logic. It has always been a pain to get meaningful data extracted out of SAP, especially on purchasing side
Having worked on both JDE & SAP i second that. Often you will have to just take the useful info able to fit into JDE tables and drop rest of it. You also need to build XREF to convert the setup values to the equivalent JDE values if they are different, which are in most of the cases. You might need multiple pass in data load before you get the satifactory load. Use Z process where available to save time and efforts.

Thanks Chan and Aarto for your valuable inputs.
Is there any suggestion on migrating the open transactions. On a high level how is this handled usually.
Thanks Chan and Aarto for your valuable inputs.
Is there any suggestion on migrating the open transactions. On a high level how is this handled usually.

Data migration from ERP (SAP/Ebus/Psft/AX etc etc) into an existing JDE instance basically goes like this:

Source all master data - eg Address book entries, AP master, assets, inventory items etc etc - you will need to determine whether the identifier used in SAP is suitable for JDE and also whether the master data already exists in JDE. For example, is the SAP supplier record the same as an existing JDE supplier record.

Map your chart of accounts - this is probably going to cause you some pain. The recommended approach is that the new BU complies with a standard corporate chart of accounts so that consolidated reporting is easily achieved. If that is not possible then you need to define a new CoA structure for the new BU and then develop consolidated reporting in some other solution like Hyperion. If you mimic the BU's existing chart in JDE be aware that you're going to have to do all of the config regarding AAI's for all of your transactions. Also be aware that SAP FI/CO and the JDE GL work in fairly different ways and the first time someone says "cost object" in a design meeting there will be some confusion for a while. It is like a JDE subledger but not...

Close out all open transactions in SAP that you can - in your case this will primarily be a clean up of procurement and AP as you're not running manufacturing, sales etc etc. So all open purchase orders need to be reviewed. Receipt whatever you can receipt and depending on the size of the business and their cash flow position you may even consider paying all open invoices even if they're not due.

Migrate transactions and balances - If you've managed to map your CoA then you can complete a month end or even a year end and then migrate those balances over to JDE (this is the last step). You should complete a full stocktake in SAP and then enter the same stocktake into JDE to get your inventory over and correct (no transactions during this time). With open purchase orders the normal approach is to cancel all outstanding amounts in SAP and then generate corresponding purchase orders in JDE and notify your suppliers that the original order has been cancelled and what the new order number is. For fixed assets you'll need to go through the normal process of loading up book values and all of the other stuff you require for loading an existing asset into JDE fixed assets.

That is pretty much it in terms of data migration. Obviously this is not a comprehensive guide so you'll need to go through all of your business processes to work out what data and transactions have to be migrated.
Hi Russell,

We are gearing up for a SAP to JDE conversion that involves 3 companies. The third company is a hodge-podge mix of different systems, - Shoplogix/VPI/MAPICS...and more. You advice above is great and I was hoping you would be so kind as to share any additional advice or documents. If you are available please let me know as the project is still in the RFP stages and we are also bringing on talent... a guy like you would be a God-Send... even remotely, as I see you are in Australia, this project is in Pennsylvania, USA ... Thanks, Steve Winnicki 479-799-5369, [email protected]

The godsend is to have some really good E1 Functional peeps (aka, probably consultants) - working with the current employees.

Hopefully, the employees know what is happening in their SAP and other applications. The E1 guys will work with them to make sure the data is mapped across and the Technical guys - will make sure the mapped data is pushed across.

Did this in 2005 - in about six months, with a smaller company. Their employees knew their data dang good. The contractors knew what was required in E1. Together they mapped out what came from SAP and where to put it in JDE. I just moved data and validated it. Overall, it went pretty smooth.

The big thing was to make sure the teams know their data / configuration.

PS - it's nice to read that an occasional SAP Migration is moving 'our way'!

I think this is the ONLY time I've heard of SAP to JDE!

Its not at all uncommon. Back in the late 90's - it was much more common. Those companies that had gone through a disastrous implementation, costing multiple millions and not being able to go live - there were many of them that came to JDE and are still on JDE today.

When you hear of a JDE to SAP conversion, its often done "screaming and kicking" by the users. Many times its because a larger organization (who currently runs SAP) acquires a smaller organization (on JDE), and the company wants to standardize - even if it means losing functionality and agility. Sometimes its companies that were persuaded by SAP to make the leap when the Oracle/Peoplesoft takeover occurred - sometimes lured by "free" licenses. Sometimes its done by a new CIO that just thinks its a good thing for their resume, with no thought for the company and the results of a disastrous expenditure.

While not all are this way, there are definitely well known examples. And there are well known success stories, on both sides. But rest assured, the number of companies moving from SAP to JDE are mostly doing it for functionality and because its been measurably identified that JDE is offering a better solution. So mostly we're not seeing "kicking and screaming" to JDE !
... Sometimes its done by a new CIO that just thinks its a good thing for their resume, with no thought for the company and the results of a disastrous expenditure...

That's the story of my previous site.
When they announced their intent, I googled "Notable SAP Failures" and got results.
When I googled "Notable JDE Failures" I got documentation.

Regardless, I agree that it's GOOD to see "SAP to JDE".
I'd like to see a lot more of it.
Tales of woe are everywhere :


(I worked with JDE on trying to sell OneWorld to Waste Management in 1999, the company decided to implement Peoplesoft at the time, and I guess they then later ditched that - probably during the Oracle takeover - for SAP, bet they're regretting not purchasing JDE now !)

Of course, the most infamously bad JDE implementation was Gateway 2000. But really, really bad implementations often are just the fault of the customer - wanting either the software to do something it wasn't designed to do, or trying to take too much scope all at once, without having any real control on their project leadership. I've seen JDE implementations that, while they DO go live (and relatively well), they are still classed as a disaster since the project exceeded budget by multiple factors. Remember, only 25% of all projects are successful for a reason....
Well Y2K was also major factor many companies had to move to ERP, most of them tried to map the legacy system exactly into selected ERP and customized to the point where it would be difficult to maintain during that short time frame.
Well Y2K was also major factor many companies had to move to ERP, most of them tried to map the legacy system exactly into selected ERP and customized to the point where it would be difficult to maintain during that short time frame.
Indeed. I have not so fond memories from the month before Y2K. Good thing that everything was sorted out rather quickly.
Dumitru SAP
Thank you, I’ve just been searching for information about this topic for a while and yours is the greatest I’ve discovered till now.