# Sage X3 Upgrade Path Checklist: Patches, Syracuse and Version Updates > Source: https://netray.co/tools/sage-x3-patch-and-version-upgrade-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A five-stage checklist for applying a Sage X3 product update or moving V11 to V12 and later releases on-premises, from component inventory to rollback. ## Category other-erp ## Erp Sage X3 ## Audience - ERP administrator - Sage X3 consultant - IT manager ## Tool **Kind:** checklist **Groups:** #### 1. Plan **Items:** **Text:** Record current versions of the application, runtime, Syracuse, print server, MongoDB and Elasticsearch **Critical:** true Read the release notes for the target release and every release skipped in between **Text:** Check the compatibility matrix for SQL Server or Oracle, Windows Server, MongoDB and Elasticsearch versions **Critical:** true Confirm the target application update, runtime and Syracuse versions are certified together Decide the method: the product update procedure documented for the target release for standard updates, and Patch integration for add-ons, partner patches and specific developments List specific and vertical developments by activity code and who owns retesting each Book a test window and a production maintenance window with business owners #### 2. Backups **Items:** **Text:** Full database backup of every folder and the X3 root, verified by a test restore **Critical:** true **Text:** MongoDB dump of the Syracuse database **Critical:** true Copy of the application folder tree on the runtime server (folder directories and specific files) Export of Syracuse configuration items you changed: endpoints, web service pools, global settings, certificates Copy of print server report templates and specific Crystal reports Note of the service accounts, ports and certificates in use #### 3. Apply in test **Items:** Refresh the test environment from production before starting **Text:** Update components in the order given by the release documentation, test folder first **Critical:** true For bespoke or partner patches, review the patch content and the objects it replaces before Patch integration **Text:** Revalidate the folders after the update, including child folders of the reference folder **Critical:** true Recompile specific and vertical processes and check the compilation log Check that activity codes protected your specific screens, tables and processes Check specific Crystal reports against changed tables Republish SOAP web services and retest REST representations used by integrations Apply any Syracuse hotfixes published for the target release #### 4. Regression test **Items:** Sales order to delivery to invoice, with pricing and tax Purchase order to receipt to supplier invoice Work order release, material issue, production tracking and close Stock count and stock transfer Journal posting, payments and bank reconciliation Period close steps your finance team runs Import and export templates and their scheduled jobs Batch server tasks and recurring tasks run as scheduled User roles: a sample of profiles can still reach their functions #### 5. Production cutover and rollback **Items:** Users disconnected and batch server stopped for the window **Text:** Fresh backups taken at the start of the window, including MongoDB **Critical:** true Same steps run in the same order as the signed-off test run Smoke test of key flows by named business users before reopening Rollback decision point and owner agreed; restore steps tested on test Version inventory and runbook updated with the new component versions **Scoring Note:** Critical items are the ones that make a failed update recoverable: a full component inventory, verified backups including MongoDB, test folder first, compatible component versions and folder revalidation. ## Content **Intro:** This checklist covers applying a Sage X3 product update or moving from V11 to V12 and later releases such as 2024 R1 on your own servers. It focuses on what is specific to X3: the component stack, the product update procedure and Patch integration, folder revalidation, MongoDB backups and specific code. **Sections:** #### How to use it **Body:** Work through the five groups in order and do the whole list on a test environment refreshed from production before touching production. Record versions and dates against each item and export the completed list as the runbook for the production window. Items marked critical are the ones that make a failed update recoverable, so do not start a production window without them. **Bullets:** - One owner per specific development for retesting. - Time each step in test to size the production window. - Keep the version inventory with the runbook. #### Where this lives in Sage X3 **Body:** Standard product updates follow the update procedure in the documentation for the target release, which also states the runtime, Syracuse, MongoDB and Elasticsearch versions it needs. Patch integration, under the development utilities for patches, loads patch files such as add-ons, partner patches and specific developments into the reference folder. Folder revalidation is run from folder management after the update so each folder picks up the new dictionary. Endpoints, web service pools and global settings are in Syracuse Administration, and the batch server is stopped and restarted from its own administration function. #### Version differences and gotchas **Body:** The stack has several parts with their own versions: application, runtime, Syracuse web server with MongoDB and Elasticsearch, and the print server. Each release states which versions it supports, and an application update can require a newer runtime or Syracuse first. Revalidation can be long on production folders because heavy tables may be rebuilt, and nobody can be connected. Patches install processes in the reference folder, so specific code protected by activity codes must be checked, recompiled and retested after every update. #### How to check the result **Body:** After the update, check the version screen and the server components show the target versions, the folder revalidation log has no errors, specific processes compile cleanly, and the batch server is running its scheduled tasks again. Then have business users run the regression list. Integrations are the most common late failure: call each SOAP publication and REST representation your partners use before reopening production. **Cta:** If you want your team to ask questions about Sage X3 data in plain English on your own servers, ready for the next update, we can set that up. **Faq:** #### What is the Sage X3 upgrade path from V11? **Answer:** V11 sites move to V12 and then onto the current V12-based releases named by year and release, such as 2024 R1 and later. Check the release notes and component compatibility for your target, update runtime and Syracuse as required, apply the application update in test, revalidate folders and retest specific code before production. #### How do I upgrade Syracuse for Sage X3? **Answer:** Use the Syracuse version certified for your target application release, plus any hotfixes Sage publishes for it. Back up the MongoDB database and your Syracuse configuration first, update in test, check endpoints, web service pools and certificates afterwards, and confirm users can log on before updating the application. #### What is the difference between a product update and Patch integration in Sage X3? **Answer:** A product update moves the whole stack to a new release: application, and often runtime, Syracuse and their database components, following the release's update procedure. Patch integration loads individual patch files, such as add-ons, partner patches or your own specific developments, into the reference folder. Both need folder revalidation and a retest of specific code afterwards. #### How long does a Sage X3 version update take? **Answer:** It depends on folder size, number of folders, specific code and how many releases you skip. Time each step during the test run, especially folder revalidation of large folders, and add regression testing and a rollback margin. Many sites plan a weekend window for production after one or two full test runs. ## Search terms syracuse upgrade sage x3, sage x3 upgrade path, sage x3 update, sage x3 latest version, sage x3 patch integration, sage x3 maintenance tips, sage x3 v12 upgrade checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json