From version > To version - default action/installation type

8.7.12.1 > 9.1.5.11 defaults to a side-by-side installation (default install folder is "PlanSwift9").

9.1.5.11 > 10.1.1.8 (or any version of PlanSwift 10) defaults to an upgrade-in-place (default install folder is "PlanSwift9"). You can change the installation folder to PlanSwift10 to perform a side-by-side installation (recommended). The upgrade-in-place means your PlanSwift 9 data visible in PlanSwift 10 upon first launch by default. If you changed the install folder to "PlanSwift10" to perform a side-by-side install (recommended), you can import your PlanSwift 9 data into PlanSwift 10.

10.1.1.8 > 10.2.5.40 is an upgrade-in-place (the folder you installed 10.1.1.8 to is where 10.2.5.40 will be installed); user is not prompted to choose/set installation folder at all, your data will be available when you launch 10.2.5.40.

10.2.5.40 > 10.2.5.41 is an upgrade-in-place (the folder you installed 10.2.5.40 to is where 10.2.5.41 will be installed); user is not prompted to choose/set installation folder at all, your data will be available when you launch 10.2.5.41.

10.2.5.40 > 10.3.0.50 is an upgrade-in-place (the folder you installed 10.2.5.41 to is where 10.3.0.50 will be installed); user is not prompted to choose/set installation folder at all, your data will be available when you launch 10.3.0.50.

10.3.0.50 > 10.3.0.56 is an upgrade-in-place (the folder you installed 10.3.0.50 to is where 10.3.0.56 will be installed); user is not prompted to choose/set installation folder at all, your data will be available when you launch 10.3.0.56.

10.3.0.56 > 11.0.0.89 (this version was pulled from distribution so we could address some issues with the installation/upgrade process) defaults to upgrade-in-place (default install folder is wherever the highest version of PlanSwift is located - if you have PlanSwift 9 AND PlanSwift 10 installed, PS 11.0.0.89 installs to the PlanSwift10 folder). You can change the installation folder to PlanSwift11 to perform a side-by-side installation (recommended). The upgrade-in-place means your PlanSwift 10 data is visible in PlanSwift 11 upon first launch by default. If you changed the install folder to "PlanSwift11" to perform a side-by-side install (recommended), you can import your PlanSwift 10 data into PlanSwift 11.

Any version prior to 11.0.0.89, upgrading to PS 11.0.0.123 defaults to a side-by-side installation (default install folder is "PlanSwift11"). Upon first launch, PlanSwift 11 detects previous versions and allows you to import your previous version of PlanSwift's data into PlanSwift 11. Remember, if you are using a custom storages location, you'll need to set it up again in PlanSwift 11 or else imported data will be added to your local storage only.

11.0.0.89 > 11.0.0.129 - defaults to a side-by-side installation with the installation folder being "PlanSwift11". If your previous installation of PlanSwift 11 (11.0.0.32 or .89) used the defaults, it was installed in the previous version's install folder and a new "PlanSwift11" folder is created. You'll be able to import your jobs and templates (just like a 10.x upgrade to 11). By default, fresh installations of PlanSwift 11.0.0.89 installed to a folder named "PlanSwift". When you install PlanSwift 11.0.0.129, the default installation folder is "PlanSwift11", and installs side-by-side with PlanSwift 11.0.0.89. Upon first launch, PlanSwift detects the older version and prompts you to import jobs and templates. Again, if you use custom storages, you'll need to set those up before you run the import. Before running the Import Utility, be sure to uninstall any version of PlanSwift other than the most current one you're using. The Import Utility only sees the oldest version of PlanSwift installed on your computer, if you have PS9 and PS10, it will only see PS9. See Using the Import Wizard to Migrate Jobs & Templates for more information.

We recommend you leave your most recent previous version installed after upgrading to a new version. Don't bring over all your Jobs, just select those you are working on or plan to circle back to. Copying all Jobs from one version to another takes up hard-drive space and makes the Open Job dialog box more difficult to use. You can always fire-up the previous version and look at old jobs, or run the Import Wizard again to select the Job to migrate it to the new version.