How do I move imos iX to a new server?
Database, shared folder, drive mapping, firewall and paths to CNC and cutting lists: how to move imos iX to a new server without surprises.
Short answer: An imos iX server migration has two parts: the SQL database and the imos data folder containing drawings and the library. You restore a database backup on the new SQL Server, copy the data folder to a new share and point the workstations to it using the same drive letter. Then you update the firewall, the connection in imos and the paths to CNC, cutting lists and ERP, and test with an existing order.
Applies to
- imos iX 2019 and newer (carried out in practice with imos iX 2019 and 2023)
- Microsoft SQL Server (Express or Standard) and SQL Server Management Studio
- CAM iX output, cutting list export and any ERP integration
- Last reviewed: October 2026
Preparation
- Agree a date with your IT administrator and the designers. Nobody can work in imos during the migration.
- List every path that points to the old server: the imos data folder (for example
Factory\ImorderandLibrary), the CNC output folders, the cutting list export folder and the import folder of your ERP system. - On a workstation, note the current server and database name in the imos iX options.
- Check that the new server runs a Windows Server version still supported by Microsoft and has enough memory for imos alongside any other software on it.
- Check the SQL Server version on the new server. It must be the same as, or newer than, the version on the old server.
You can restore a database backup on a newer SQL Server version, but not on an older one. Never install a lower SQL version on the new server than on the old one.
Moving the database
- Ask all designers to save their drawings and close imos.
- Back up the database on the old server. See imos iX database backup and restore for the procedure.
- Is SQL Server not yet installed on the new server? Install it from the imos iX installation media, including the imos data and standard database.
- Install SQL Server Management Studio on the new server, in a version that matches your imos iX version.
- Restore the backup on the new server, following the same article.
- Check the growth settings of the transaction log. A maximum size that is too tight will cause errors later.
Making the database reachable on the network
- Open SQL Server Configuration Manager on the new server.
- Set the TCP/IP protocol to enabled.
- Open the TCP/IP properties and note the dynamic port shown at the bottom.
- Open the advanced settings of Windows Firewall and create a new inbound rule of type Port.
- Open TCP 1433 (the SQL Server default), UDP 1434 (SQL Server Browser) and the dynamic port from step 3.
- From a workstation, test whether you can log in to the database with Management Studio. If you can connect straight away, the connection is open.
Switching the data folder and workstations
- Create a share on the new server, for example
\\SRV-FILE\imos, with read and write permissions for all imos users. - Copy the entire imos data folder from the old server to the new one, for example using
robocopywith the/Eoption so all subfolders are included. - Point the drive mapping on every workstation to the new share, using the same letter as before (for example
I:\). - In the imos iX options on each workstation, update the server and database name, for example
SRV-SQLandIMOS_DEMO. - Update the CNC output folder per machine via Productie-instellingen → Machine → Toon eigenschappen → Doelmap (production settings, machine properties, target folder) if it still points to the old server.
- Check the configuration file of the cutting list export (for example in
I:\CUT) for paths to the old server, and align the import folder with your cutting software supplier. - Check the imos.ini used by any ERP integration for references to the old server.
Testing and wrapping up
- Open an existing order on at least two workstations and generate the CNC programs; check that they land in the correct folder.
- Generate a cutting list and import it into your cutting software.
- Test the import into your ERP system with a test order.
- Together with your IT administrator, set up a daily automatic backup of both the database and the imos data folder.
- Only switch off the old server once everything has run without problems for a few days.
Keep the drive letter the same. If every path in imos runs through I:\, you only need to change the drive mapping after the move.
Why this approach?
imos iX stores its data in two places: master data, articles and orders in the SQL database, and drawings, connectors, images and settings in the data folder. Move only one of them and imos will only half work. That's why we treat them as a single migration.
In practice, we often see the database moved correctly while CNC programs or cutting lists are still written to the old server. Those paths live outside the database, in machine settings and configuration files. You only notice when the old server is switched off. So list those paths up front.
A server migration is also a good moment to look at performance. In one speed test, opening a drawing from the server took almost four times as long as opening it locally, while the database location made little difference. The bottleneck was the transfer of the drawing files. Put the data folder on fast SSD storage, not on a NAS or in a cloud folder.
Common mistakes
- Moving only the database. The data folder with drawings and library must move too, or orders will open without connectors and images.
- Choosing a different drive letter. Every path in imos then points to a location that doesn't exist.
- Opening only port 1433. A named SQL instance also needs SQL Server Browser and the dynamic port.
- Forgetting CNC and cutting list paths. They live outside the database and still point to the old server after migration.
- Not setting up a backup on the new server. Agree beforehand who is responsible.
Frequently asked questions
Do I need to relink the licences after a server migration?
Licences are managed through the imos licence portal and are linked to the workstations, not the server. If you replace workstations at the same time, unlink the licence first. Either way, make sure the licence account login details are at hand.
Can I run the old and new database side by side for a while?
Yes. Use a separate shortcut or configuration per database and always start imos through the right shortcut, so the settings for the correct database are loaded.
Can I keep using SQL Server Express?
Yes, as long as the database stays below the 10 GB limit. If you're close to it, a migration is a good moment to clean up the database or move to a paid SQL Server edition.
Further reading
- imos iX database backup and restore
- imos iX slow? What can I check myself?
- How do I link my imos iX licence?
- imos iX consultancy
More than one solution
Almost every question in this knowledge base has more than one solution. The best fit depends on your workflow, machinery and integrations. Not sure which applies to you, or are you using software we don't (yet) support? Feel free to email Wood Intelligence. We're happy to think along with any challenge.
imos is a trademark of imos AG. Wood Intelligence is an independent consultancy.