top of page

Deployment Options

Summary

​

You can deploy an Acumatica ERP instance (the source code, the database schema and maybe some configuration data or a full demo data snapshot) in the following three ways:

  • On your own server

  • On a hosted server

  • As SaaS, which is basically on a server that Acumatica runs in the Amazon Web Services public cloud. 

​

We will discuss each deployment option next.

On Your Own Server

​

Basically you need to install Microsoft SQL Standard server 2016 or 2019 first on your MS Windows Standard Server 2016 or 2019. Once you have purchased either a permanent license (PCL - one time license) or a prescription license (PCS - monthly license) from us, you can download the Acumatica ERP instance software from the Acumatica  customer portal. 

​

We recommend to  install a PCS license on your server for the following purposes:

  • Training purposes

    • You will need to install the data snapshot that is required for a specific course eg. Finance 100 (F100). ​

    • You can create several companies (tenants) within an Acumatica ERP instance where each company  is used for a particular course with a specific data snapshot

  • Prototyping/pilot purposes 

    • You can install another ERP instance for piloting, load some of your own data, and play with the Acumatica ERP suites and modules.​

  • Testing purposes​

    • You can install another ERP instance  for loading all your data, and test it in parallel with your current system​

    • You can install yet another ERP instance for installing customizations and ISV apps

    • Once everything works really well, then you should cut over to a production mode for which we recommend a SaaS deployment. You can keep an ERP instance on your server as a backup with a standby PCS license. Actually you may also keep it for further training, customization and testing purposes since you will need to take updated training classes, and you will most probably test and implement new customizations and ISV apps.

​

The video (10 mins, 2014) below will show you how to install it on your server. The video is old, but the steps are still the same. Once MS SQL is installed, the installation of the Acumatica Cloud ERP Foundation takes only about 30 mins. Then you start to configure each suite. We will help you. An online implementation guide is available. 

On a Hosted Server

​

You can deploy an Acumatica ERP instance (the source code, the database schema and maybe some configuration data or a full demo data snapshot) on a hosted server such as Amazon Web Services, (AWS), Microsoft Azure, Rackspace, Google Cloud, Liquidweb, etc.

Most probably you can use PaaS where MS Windows Server and MS SQL server will be running already on a Virtual Machine (VM). You will have to install the Acumatica ERP Foundation software on that VM. We will help you.

​

You could install Acumatica ERP instances on the hosted server for training, prototyping and testing purposes. Once you go into production, we do recommend you to switch to SaaS. You can keep the Acumatica ERP instance on your hosted server as a standby with a standby license. Actually you may also keep it for further training, customization and testing purposes since you will need to take updated training classes, and you will most probably test and implement new customizations and ISV apps.

​

The advantage of a hosted server is that you don't have to worry about maintaining hardware, MS Windows Server, MS SQL and viruses. The hosting company will take care of that. You should purchase a backup and restore plan for your VM.

​

The installation procedure of the Acumatica ERP instance maybe the same as for your own server. It is a bit different for MS Azure as seen in the video below.

On SaaS

​

When you buy a SaaS license, all software is already installed  on the Acumatica server at AWS. You will get an admin user id and password, and be ready to go. Of course configuration still needs to be done. We will help you.

​

Backup is taken care of automatically. A lot of questions about the SaaS deployment and subcription are answered by Acumatica on its SaaS FAQ webpage.

Why SaaS for Production?

​

The following experiences explain why you should deploy your ERP instance in SaaS when you go to production:

  • Your ERP Database crashes during an upgrade to a higher version

    • Bad emails can crash your ERP SQL database. It can take 4 days before Tech Support can fix. it. Why?

      • Tech Support has to find out what the cause is of the problem. You will have to perform an application performance and upgrade in the ERP Config. wizard.This might be an hour.

      • If it is determined that the SQL DB crashed, you have to make a copy of the SQL DB in the SQL Management studio, which can take 1 hour.

      • You need to upload this DB copy to Tech Support. A DB can be 35 GB. To upload such a DB you need to set up a FTP server, or a FTP client that talks to the FTP Server at Acumatica Tech Support.

      • Acumatica Tech Support needs to analyze the problem once they have the DB copy. This takes about 2 days since they have to set up an ERP version that is exactly the same as your ERP version.

      • Once Acumatica Tech Support has found a solution that works, they will give you the solution SQL scripts to fix the SQL QB.

      • You need to have some SQL knowledge to run the SQL scripts.

      • Then you run again the Perform application maintenance and upgrade.

      • You test the fixed ERP instance

  • Your customization crashes the ERP instance on your hosted server

    • Your new customization can crash the ERP instance. In SaaS you will have a sandbox where you can test your new customization

  • A backup ERP instance is needed when you don't use SaaS

    • Your backup ERP instance needs to be the exact same version as your production ERP version to be able to import and restore a snapshot backup. When your snapshot is larger than 35 GB, you can not import it anymore. Then you have to make a SQL DB Backup.

    • A SQL DB backup is recommended to take care of customizations, and when upgrading from one major version to another major version.

    • A SQL DB backup may easily reach 100 GB. Storing several back ups will quickly deplete your 1 TB hard drive.

bottom of page