CirrusPrint 2.0 users can migrate their configuration to version 3.0 with little effort, following these steps:

Conversion Steps

The command line option to export the 2.0 configuration was added at version 2.0.19, so the first step is to update to 2.0.19.  This is accomplished by downloading and installing the current 2.0 server release from Most installs will also have updates automatically downloaded and can install one following instructions in the admin browser interface, Site, Status, Updates tab.

You must be an administrator or root user to perform the next steps.

Open a command window or terminal and change to the CirrusPrint 2.0 directory then run:

cp20s -exportconfig -o cirrusprint2.config 

Use any file name you like for the output argument, and if you want to export a single company, add a -compid option:

cp20s -exportconfig -o cirrusprint2.config -compid Acme

Now you have a file containing the configuration for CirrrusPrint 2.  Be sure to keep this file safe and secure, as it contains plain text passwords.  Once done with the file, you may want to delete it.  Move the file to the CirrusPrint 3 directory, then run:

cp30s -convert cirrusprint2.config -o convert.log

This will import the entries in cirrusprint2.config and write log lines to convert.log.  Note if a company found in the file exists already, such as if you have previously set up the company manually, and you wish to overwrite that company configuration, you can add -force to the above command line.

That's it.  The company or companies you exported are now defined in version 3.  Note however that input sources are disabled by default to prevent accidentally conflicting with a running version 2.  To enable these, use the version 3 admin browser interface, input sources, and enable the sources needed.  Note you can select multiple rows from the input source list using control-click or shift-click actions, then enable them in bulk with the "+" option on the toolbar.

Notes and Caveats

Before importing via the -convert step you probably want to activate version 3 with a license obtained from  The reason is that as output devices are imported, if the count exceeds the license (which defaults to 2 free output devices) then devices are imported in a disabled state.  If your license is activated ahead of time, this won't happen, and it will save time later.

The conversion only converts company data, including locations, input sources, and output devices.  It does not convert site data such as site users and the global mail sending configuration.  Those settings are defined manually in CirrusPrint 3.

CirrusPrint 2 and 3 cannot share input sources.  This means if you want to run both simultaneously, you need to look at your input sources and decide which should be reconfigured.  For email sources, a second email account would have to be created, along with related aliases or mail groups.  For path and port input sources, you can define new paths and ports, or else put version 3 on a different system.

To avoid this, most users opt to turn off version 2 and switch to version 3.  Some quick testing should confirm all is working as expected, but if not, you can turn off version 3 and turn on version 2 and be back where you started.

To turn on and off the servers on Windows, you can disable and enable the respective services.  On Linux, most systems use the systemd system, so can use the systemctl program to enable and disable the respective services, named cp20s and cp30s.

While the CirrusPrint servers cannot monitor the same input sources, the version 2 and 3 clients can coexist and run simultaneously.

Microsoft 365 IMAP Authentication

Some users are upgrading to version 3 because Microsoft 365 is removing support for password-based authentication for IMAP accounts.  Version 3 supports the new authentication feature termed "modern authentication".  To enable this feature in version 3 IMAP input sources, please follow the guidance in this article: