How challenging is it to upgrade to NetSuite OneWo...
# general
j
How challenging is it to upgrade to NetSuite OneWorld if the company was initially set up without it? We have some custom scripting and customization in our current NetSuite instance that was set up without OneWorld. Does upgrading to OneWorld have the potential to disrupt or break these customizations? Could we upgrade the SandBox instance first, and iron out anything in that environment first while keeping production as non-OneWorld, and then when satisfied, upgrade Production, and complete work/finalize production?
m
Depending on the new subsidiary structure you need it can be quite simple to implement
You can definitely do the upgrade in Sandbox and test before doing it in production. (In fact Netsuite highly encourages this)
There are a lot of things to consider when making this change, but if you are going to be keeping/sharing the same COA, Customers and Vendors then the hardest thing to consider is most users are thouroughly confused by the multi-subisidary setup However, if you need multi-currency, multi-book, or some huge subisidary structure it can get quite complicated to implement
Most cases of this I see it is these basic steps 1. Setup Subsidiaries 2. Merge chart of accounts 3. Setup intercompany accounts in intercompany automation 4. Merge Segments (ie departments, classes, locations) 5. Merge Customer List 6. Merge vendor List 7. Merge Item list 8. Setup Users and Roles 9. Go Live 10. Enter Historical Balances for new subsidiaries
Of course if you have more advanced features the complexitiy will continue to grow, so a lot depends on your business
j
Thank you @MGBC - this makes a lot of sense, really appreciate this insight. The use case is that we have an additional subsidiary that is in India and uses INR. Previously the company was just one entity in the US with USD. Is there any other workaround or options other than upgrading to OneWorld? I'm just trying to consider all options, especially considering the cost of the upgrade
m
I’ve seen people use custom segments or Dept, Class Location to try and mimic the subsidiary feature but it can get tricky
It can be hard to get permissions and reporting correct if you try it this way but I’ve seen it work
One world is definitely the recommended path
f
Another thing to consider, if you have a script which creates any transactions, then the script will also need to be updated. Because there is no Subsidiary field on the Non-OneWorld, but it is a mandatory field in the OneWorld environment. I agree with Maven, OneWorld is the recommended way, mimicking an entity as a segment is challenging in a lot of things
j
Thank you both for your insight and help, hoping we can go the oneWorld route