The initial setup was pretty straightforward. Even the customizations that we made, we were able to identify some ahead of time and we incorporated them as part of our implementation right in the live system. I would say, in condensed timing, we were able to migrate from a legacy system and get NetSuite up and running at about seven months, which is outstanding.

Our deployment plan was basically to scrub our existing data. We made sure that we stuck to the scope of the project - the things that we had to have live such as the functionality, the movement of data from one place to the other, making sure that the setups and the reports were there, and that the training and the testing were done. We stuck pretty closely to our strategy and plan for a go-live. Just a couple of days after we moved all of our ending balances from one system into NetSuite, we tied them out as beginning and ending balances. We were able to then start to process. 

For the most part, it was good. It wasn't exactly seamless. Everybody says seamless, however, nothing's seamless. It went as well as you can possibly imagine as most of these migrations usually take a year or more. I've been involved in a number of them over the course of time and this was pretty quick. I would also say that our consultants or integrators were very, very good. They were like an extension of us, which was a critical factor.

The initial setup for NetSuite OneWorld was straightforward, so setup-wise, I'm rating it as eight out of ten.

The time it takes to deploy the solution depends on the complexity of the organization. To implement the entire financial environment for NetSuite OneWorld, you're probably looking at a minimum of ninety days, including the planning. I consider the deployment time for NetSuite OneWorld quick.

The solution was not too bad to set up and implement. We used Cognizant and ended up learning it ourselves. The deployment took six months to complete which is quite fast. There were two to three of us on the deployment team. I was the program manager and hence took over the lead of the implementation. Another person from the product team also joined us. We were involved in the deployment while doing other jobs as well at the same time.

The initial setup for NetSuite OneWorld is somewhere in the middle in terms of difficulty level. It's a five out of ten.

Initially, my team used to do a lot of onsite visits, but in the last two years, with travel reduced, most of the deployment was done offshore rather than onsite. You can deploy NetSuite OneWorld without being onsite.

For one project with a smaller client, deployment takes around four to five months, and bigger projects take up a lot more time in terms of deployment.

When a client signs a contract with NetSuite, NetSuite assigns a project manager and a team to implement NetSuite OneWorld. My company starts the implementation process with the client through several meetings, from the project kickoff meeting to the requirement gathering and walkthrough sessions. My team then does the configuration in the system, the client will do UAT, and then my team will do the cutover activities, and then it goes live.

There are complexities, and many of them are avoidable with an established consulting team. 

The initial setup was both straightforward and complex. We added a lot of custom fields which created our own complexities.

The initial setup is pretty straightforward.

It is really the simplest ERP tool that I set up. I think it is medium complexity because I know NetSuite well and understand the requirements as well.

The setup was very complex, because we have very complex requirements, especially in accounting. A business with simple requirements could be up and running very quickly.

The installation is straightforward and it took more than one and a half hours.