Upgrade Portfolio Slicer to new version

Overview

Upgrading Portfolio Slicer is usually a controlled migration rather than an in-place replacement.

The safest approach is to install the new version separately, confirm that scripts and external data still work, and then copy your portfolio data into the new workbook structure.

  1. Back up your existing Portfolio Slicer files.
  2. Install the new version in a separate location.
  3. Review the migration to v3.x from older version for version-specific changes.
  4. Update your psConfig.txt configuration for the new environment.
  5. Run the external data scripts and confirm the generated files still look correct.
  6. Copy your portfolio table data from the old workbook to the new workbook carefully.
  7. Refresh and validate the new setup before relying on it.

What to Back Up

Before upgrading, back up:

  • your current workbook files
  • your psConfig.txt
  • your PSData folder
  • any custom scripts or manual adjustments

Do not skip this step. It gives you a clean fallback if the new version behaves differently than expected.

Configuration Checks

When moving to a new version, confirm that:

  • your psConfig.txt contains all required sections for the new release
  • output paths still point to the correct PSData location
  • symbols, currencies, and source settings are still valid
  • any new version-specific parameters have been added

Copying Data to the New Workbook

When copying your table data:

  • compare the old and new table structures first
  • do not assume columns are identical across versions
  • preserve formulas and built-in structure from the new workbook
  • copy only the user-maintained data fields that belong in each table

If a new version introduces structural changes, update your migration approach accordingly instead of forcing old data into the new layout.

First Validation After Upgrade

Once the migration is complete, validate the new version using a few key checks:

  • expected symbols appear in reports
  • holdings quantities look correct
  • values and currencies look reasonable
  • refresh completes without unexpected errors

Start with the Holdings report and work outward from there.

Version-Specific Notes

Some upgrades are simple and some are not. Always read the current migration to v3.x from older version, especially when moving between major versions.

If the new release changes workbook structure, reporting workbooks, source workbooks, or script behavior, treat the upgrade as a migration project rather than a quick file swap.