Setting up NetSuite ERP is pretty straightforward. It's a plug-and-play solution that comes with the default bundle. We uploaded our GLs and charter accounts and added our company code to the architecture. It can be up and running in under a month.  It takes at least five people to deploy NetSuite.

For one entity, on average, the deployment of NetSuite ERP takes one and a half months to two months, including the UAT and production.

For the initial setup, we enlisted the help of a consultant—a specialist assisting us in configuring the system. I find the process complex, particularly in comparison to platforms like Salesforce.

The solution is deployed on the cloud.

The solution's initial setup process was complex.

It's a SaaS product, so we don't have to deploy it to any product here. It's something that is managed by the company itself.

It took some time to spin up, however, it was, I would say, easy to medium complexity. Out of five, it was like a 3.5 in terms of ease of setup.

Setting up the system may be difficult for customers since they will need assistance from a partner. However, once the solution is set up, the customer is able to manage the system more easily, such as by creating reports and enabling features. To begin, customers must depend on a well-trained partner team to do all of the necessary developments, but they will be able to manage the system independently after it is up and running.

Following Oracle's guidance, the process is easy to understand. Once a customer signs up and the necessary licenses are obtained, a common work page is created where everyone can log in and receive admin access. After this, the modules are deployed and configured for the customer. There is no need to configure complicated algorithms as everything is already predetermined by Oracle. Once the modules are enabled, custom configurations can then be applied. The process is neat and centralized.

For a simple deployment without any advancements, the implementation can be completed in three months. 

A single expert in project management with knowledge of the business should suffice for the task. Two members may be used, with one specialized in technical and the other in functional aspects. This does not require a lot of resources to be allocated. If a techno-functional consultant who is familiar with NetSuite is available, then one consultant should be sufficient.

It's a software-as-a-subscription solution. It has a very straightforward setup. I would rate it a nine out of ten in terms of ease of setup.

The setup process mostly depends on the type of VAR that you have. If you have a good VAR with competent engineering capabilities, your implementation could be a dream. But if you're like me and you have a VAR that is horrible, unresponsive, lacks the skillset, is completely unhelpful, and likes to point fingers, then you're going to have a very difficult implementation that's going to turn into a nightmare.

We were doing an integration with Stripe, which was a horrible experience. Stripe is a poor product, so it was very difficult to engineer that kind of data integration. Most of the VARs are not capable of handling that kind of environment. 

Time-wise, it can really depend on how long the deployment can take. If you're not trying to integrate it with a platform like Stripe, then you can have an easy implementation. That really depends on how much data you're trying to integrate, in terms of historical data. In the United States, we have laws around Sarbanes Oxley requirements. So there are certain steps that you have to follow to make sure that you have the right amount of data. When you do a new ERP system, you're really kind of concerned with the functionality in your reporting. So if you have transactions going through the new system, but you don't mirror them in the old one, you're never going to know whether or not what you're trying to do can be comparable to the old way, which is something you've relied upon and you have. It's like a test case, for example.

The initial setup is easy. However, if your company works with a standard environment and has well-defined processes, then you can easily map the system. It's like an off-the-shelf product that you can buy and use, almost like a plug-and-play solution. 

However, if your company has some extra requirements or needs to map certain areas into the system, then it can be troublesome. That's the case with NetSuite ERP. In contrast, Microsoft Dynamics Business One doesn't have that barrier.

Another significant difference is the licensing. With Microsoft Dynamics Business One, we can use Test more licenses, which allows for extended testing periods. However, NetSuite doesn't provide that kind of facility. While they may have trial options, you have to pay for subscriptions and hosting right from the beginning when implementing the product. This might cause budgetary challenges for some companies during the implementation process.

I rate NetSuite four out of 10 for ease of implementation. It's difficult to implement but easier than some other ERP solutions. 

Everything's complex today. It's all complex. Any system is complex. However, NetSuite's setup, what makes it easier, is there's not a lot of complexity in the actual customization. That's easier. Any system, even Microsoft's Dynamics, is going to take 30% or 40% more labor to do the same things. 

NetSuite's highly configurable and it's also very structured for settings, presetting, roles, permissions, personalization, etc. If the partner that's selected is skilled, if they know the system, then the configuration works actually in a pretty straightforward manner. 

There may be a lot of variabilities or a lot of complexity, mainly because clients are complex. Nobody does things the same way. If they did, they'd run out of business pretty quick due to the fact that you always have to have something that differentiates you from your competitor. All those differentiations have to be thought of and incorporated into the implementation.

The product's deployment is simple since it is a well-documented solution. 

Setup is straightforward. The methodology is extremely important. If the core business model and financial strategy is implemented correctly, all other modules become sequential building blocks.

The initial setup is not overly complex or difficult. It's simple and straightforward. 

The initial setup has improved. Concerning what I know about it from 15 years ago to now, it's fairly straightforward. It's a lot more streamlined. There are not as many customizations you can do. You can create a few fields and add things here and there, however, when it comes to really create custom processes it forces you to use workflows and things like that. It's simpler in that it provides a lot more visibility to the business of how their processes work.

The initial setup is complex. I would recommend that any company making a switch to NetSuite look to get help from a NetSuite VAR (Value Added Reseller).

The initial setup was more or less straightforward for NetSuite. It needs to be handled properly considering the clients' requirements.

The process started with getting support from them. Then we carried out the implementation in the vanilla environment for wholesale distribution; after which I developed the SDN certified NetSuite Education ERP product (edERP). So in terms of customization, I have worked from a simple to complex level.

The setup was reasonably straightforward. It's all in the planning. If you plan what you want, it's easier to hit the target.

The setup depends on the complexity of the business. I’ve seen customers up and live on this system in as little as two weeks. I’ve also seen implementations that go on for six to nine months.

There seems to be no problems with initial setup, but not sure if you are trying complex cross-functional process. There could be a concern about the cost of consulting for optimal configuration of process.

The initial setup was easy. 

NetSuite ERP is straightforward to implement, however, it can become really complex. You could decide to use it out of the box, but if you really want to make it complex, you have the ability to. Sometimes you need to think about not going overboard with everything.

The initial setup is always very important. It is not as complicated as a few other applications, and it was easier to execute it. The complexity comes when multiple processes and multiple workflows need to be created for the automation to come in. To kickstart it quickly, it is much easier compared to other competitor products in the market.

The installation is easy.

The setup was straightforward. The implementation team will work with the system administrator to configure this tool to your company's needs. Be sure to have a clear idea as to how you would like the system to work.

The setup was straightforward. The Oracle help center explained everything to us.

The initial setup was simple.