Sage 300 CRE users have been relying solely on on-premises servers to manage their data for many years. But now, since cloud technology has become the standard for business operations, many companies are exploring how to actually move their Sage data into modern cloud environments.
Some users also want to move to the cloud because Sage’s own reporting is slow, especially now when the speed of processing has multiplied. When you need to run a detailed job cost report or fetch data across multiple projects, the system might come to a halt.
But the challenge is that information about this specific migration process is surprisingly scarce or spread out in fragments. Many IT teams and business owners are unsure of how to make this migration.
When they Google “how to migrate Sage 300 CRE data to the cloud”, they get results for moving Sage 300 CRE from one on-premise server to another.
This won’t be the issue anymore because this guide answers how to migrate your Sage 300 CRE data to a cloud warehouse. We’ll introduce you to a step-by-step migration process.
Before we start with the method, there’s something important you should know.
The phrase “moving Sage 300 CRE to the cloud” can mean two different things. And it’s common for people to confuse them with one another. So let’s first make it clear what those two things are and which one is our main focus.
The Two Types of Sage 300 CRE Migrations
Migrating Sage 300 CRE can imply operational cloud migration, where you move your entire Sage application to run on cloud infrastructure. Your ERP still works exactly as before, but instead of running on a server in your office, it runs on a virtual machine in Microsoft Azure, AWS, GCP, or another cloud platform.
The second implication is data warehouse migration. Here, you extract only your Sage data and push it into a cloud data warehouse like BigQuery or Azure Synapse for reporting and business intelligence (BI) purposes. This type of migration is usually done for better performance. The new high-performance cloud warehouse makes a copy of your Sage data and generates reports from it quicker than your on-premises Sage setup.
Our primary focus is on this second approach, as is clear from the title of the article as well. Though we’ll also briefly explain the other method, the full Sage migration.
How to Migrate Your Sage 300 CRE Data to a Cloud Warehouse
To migrate Sage 300 CRE data into a cloud warehouse, you typically use ETL connectors. ETL stands for Extract, Transform, and Load.
Here’s how ETL connectors replicate your Sage 300 CRE data to cloud warehouses:
- First, they extract the data from Sage 300 CRE via APIs, drivers, or direct connectors.
- Then the data is transformed and loaded into a cloud warehouse (e.g., Snowflake, Databricks, Azure Synapse).
- Lastly, they enable analytics/BI on top of that warehouse.
Many third party tools exist that offer ETL connectors for Sage 300 CRE.
For example, Anterra Technology offers Anterra Data Center (ADC), which can pipeline Sage 300 data continuously into a Microsoft SQL Server database that runs parallel to Sage’s existing Pervasive database.
Here’s more about how you can implement ADC to migrate your Sage 300 CRE data.
Extracting Sage 300 CRE Data with Anterra Data Center
As you read, ADC continuously replicates your Sage data into a Microsoft SQL Server database that runs parallel to your existing Pervasive database.
This replication happens in real time. The Microsoft SQL Server will always have the most recent data without requiring manual exports or scheduled batch processes.
In addition, your reports will also load faster because SQL Server is purpose-built for handling queries quickly. Sage’s own Pervasive database is slow because it prioritizes transactional integrity over performance. Anterra’s ADC simply replaces this Pervasive database.
So, when someone needs to run a report, they query the SQL Server version of your data, not the Pervasive database.
Your Sage 300 CRE system keeps operating exactly as it always has, with the only change being a high-performance reporting engine working alongside it.
Now let’s introduce you to the ADC setup.
Anterra Data Center Setup
Before installing ADC, you need several software components in place. The following table summarizes those requirements:
| Component | Requirement |
| Sage 300 CRE Version | 17.1 or newer |
| Sage ODBC | Installed with purchased license |
| Microsoft SQL Server | 2016, 2017, 2019, or 2022 (Express editions supported) |
| .NET Framework | Version 4.8 (installs automatically if missing) |
| Operating System | Windows 10, Windows 11, or Windows Server 2016/2019/2022 |
| Processor | 2 GHz multi-core minimum, 2.5+ GHz recommended |
| RAM | 6 GB minimum, 8 GB recommended |
For the SQL Server database, plan for hard drive space roughly equivalent to your Sage data size. To be on the safe side, you should double that amount to accommodate transaction logs, indexes, and temporary files.
Anterra Data Center Installation
Once you have taken care of everything, here’s how ADC installation goes:
- Create a dedicated user account in Sage 300 Security with Application Administrator permissions. Set the password to never expire so you do not need to update scheduled tasks when passwords change. Test the credentials by logging into Sage Desktop with the new account.
- Install Microsoft SQL Server if not already present. For datasets under ten gigabytes, SQL Server Express works fine and costs nothing. ADC uses two separate databases: one for extracted Sage data and one for extraction configuration settings.
- Decide where to install ADC. The recommended approach is installing it on the same server where Sage 300 resides. You can install it on a different computer and access Sage data folders through a UNC path, but this configuration does not support scheduled updates.
- If your SQL Server runs on a different machine than ADC, configure a shared folder on the SQL Server for bulk insert files. The SQL Service account needs read access to this folder, and the Windows account running ADC needs full read and write access. Also ensure the MS SQL Service logs on using a domain account rather than the local service account.
- Run the ADC installer. The installation typically completes in thirty to forty-five minutes. The software needs db_owner permissions on the SQL databases it creates.
- Configure your synchronization schedule. You can sync continuously throughout the day, run updates during off-hours, or trigger syncs on demand. After the initial full synchronization, only changed data transfers, so daily updates typically finish in ten to twelve minutes.
ADC synchronizes all your Sage 300 CRE data, including every accounting module like General Ledger, Job Cost, Accounts Payable, Payroll, Accounts Receivable, and others, plus additional modules like Service Management and Purchasing.
Anterra offers a fourteen-day free trial so you can verify performance improvements with your actual data before committing. Anterra’s support team assists with installation and can help determine which service tier fits your data volume.
You can schedule assistance with your ADC install by submitting this Setup Information Form.
If you’re attempting the migration right now, here’s AnterraDataCenter Prerequisites Documentation with all the technical information.
Bonus: How to Move the Sage 300 CRE Itself to the Cloud
While moving Sage 300 CRE data to a cloud warehouse solves reporting challenges, some companies also want to move the Sage 300 CRE application itself to a cloud-hosted environment.
This operational cloud migration means your Sage application and database both run on cloud infrastructure instead of local servers.
Sage Partner Cloud supports deploying Sage 300 CRE on cloud platforms, including Microsoft Azure, AWS, and Sage-accredited providers like Cloud at Work, Swizznet, ADSS Global, Bennet/Porter, CBIZ, RKL Solutions, and SWK Technologies.
These providers have been vetted by Sage and meet specific security and compliance standards.
Here’s a quick summary of this migration process:
- Copy your files to a new server that happens to be in the cloud
- Run the Sage installers
- Update the configuration in Database setup
For the database itself, you can use Sage’s Dbdump and Dbload utilities to export and import your data. Or if you’re running SQL data alongside Pervasive, you can use standard SQL backup and restore procedures.
All your other Sage files simply get copied to the new cloud server. The configuration changes mainly involve pointing Sage to the correct database locations and ensuring network paths are set up properly.
Sage supports the Sage 300 CRE product itself when running in cloud environments, but does not set up, configure, or troubleshoot the cloud infrastructure. For that, you need either your own IT professionals or assistance from a Sage Certified Consultant or Business Partner.
Another critical consideration is how users connect to the cloud-hosted Sage system. Sage strongly recommends using Remote Desktop Protocol (RDP) connections rather than VPN connections. The reason is reliability.
If a VPN connection drops unexpectedly while someone is working in Sage, it can lock files and potentially damage data integrity in the Pervasive database.
RDP connections are more stable and less prone to these sudden disconnections. You can still use VPN to establish the initial connection to your RDP session, which Sage considers a reliable approach.
ADC Could be Enough for You
Migrating your entire Sage 300 CRE to the cloud might be looking more tempting to you.
But Anterra’s quick and simple ADC add-on could be solving the same issues you expect the full cloud migration to solve. So before committing to full cloud migrations, make sure you’re actually facing big enough problems to warrant that type of complex and expensive migration.
If not, simply migrate your Safe 300 CRE data only using ADC.
It gives you SQL’s fast speed without replacing anything.
Your existing Crystal Reports transfer over, and your team avoids a steep learning curve. They keep working the way they always have, just with better tools alongside.
And remember, Anterra has a 14-day free trial of Anterra Data Center. So book a demo with Anterra and let the results speak for themselves.