On a scale of one to ten, where one is difficult, and ten is easy, I rate the initial setup a ten since it is an easy process.

The solution is deployed on a public cloud by AWS.

The deployment process can take a long time, considering the end part of the implementation process required for the tool. For a simple setup using AWS, one to two days are needed, but a standard implementation would take four to six months.

Around 8 to 10 people in my company are involved in the product's deployment phase.

I would rate my experience with the initial setup around seven to ten for the setup, one being difficult and ten being easy. We prefer cloud deployment.

The solution's initial setup process was easy.

The initial setup is very easy. If you are very familiar with the product then it will take you less than an hour to deploy. Integrating it is also easy to do. The majority of time for deployment would be with the installation itself, as opposed to the configuration because it is very straightforward.

In total, it will take less than a day to fully deploy on the cloud.

The initial implementation was a collaborative effort, but as time passed, our team, including individuals like me, has become increasingly self-reliant in terms of generating reports and handling technical aspects.

The initial setup of the product seems to be good.

The solution is deployed on the cloud services offered by AWS.

The setup was a complex project because we hadn't previously worked with this type of tool. The integration of data and learning how it worked was the complex part, but the tool was very useful. We considered the setup to be very fast, but our internal process to use the software took us a little while. Our configuration only took three months, but it took us four more months for the full implementation.

The initial setup is not very difficult, but one needs to have the data and know their requirements before setup, as once it is set up, then one has to continue with that. So the better you know the data and know your specific needs, the better. I was not there during the deployment, but They went live on the first of March but were only actively processing only from the first of May. So the first two months were just so generalized from the previous application.

We implement the tool for customers. It is effective. We can configure the business processes much faster for medium-sized businesses. Switching from Excel-based manual work or legacy systems to SAP was fast, smooth, and easy. The deployment is straightforward. The time required for implementation is reasonable.

Currently, our partner's performance is satisfactory; they are competent and reliable. It took almost six months.

The initial setup is easy. Once HANA came into the picture, It became more manageable for scaling with security and scalability.

Deployment is pretty straightforward when it comes to SAP implementations. We follow a five-step method to understand the configuration requirements of the customers and the business process, and then we make a document called the Business Blueprint. The outcome is used to configure the system, which is a configuration development phase. We ensure we configure, develop, and deploy whatever this customer requires. When we get a sign-up from the customer, we move to training and data migration. When we launch this for users, and we support the users from that point of time till the time, the adaptability is very high.

The initial setup is straightforward. However, it takes a lot of time to deploy.

The initial setup is straightforward and takes approximately two to three months to complete. The most time-consuming aspect of the deployment is collecting all the business requirements to properly configure some of the existing workflows.

The initial setup was easy.

The initial setup is manageable.

The initial setup of SAP Business One on AWS is relatively easy. The full implementation took us approximately six months.

SAP Business One on AWS's initial setup is simple.

The initial setup is rather straightforward even though we have been struggling with a few issues. 

As my company started to use SAP Business One on AWS, Amazon's partner helped us to configure a few things.

Whenever there is a need for installation, my company reaches out to AWS' partner, especially since our systems will be in HA mode. My company did not find any issues in the aforementioned area. Only when my company wants to upgrade or downgrade does it reach out to AWS' partner, which happens one or two times.

This solution has its own complexities because it is an ERP system, but the current version is pretty straightforward. That said, you will still need external help, as you probably couldn't do with internal IT teams.

The length of time to deploy can take anywhere from 15 or 20 days and above.

The initial setup was straightforward. Deployment took around three months.

Setting up Business One is straightforward. It took us about three months to deploy Business One on AWS.