Best Practices for Migrating Your PI System from 32-bit to 64-bit

Migrating your PI System from a 32-bit environment to a 64-bit one is a critical step forward for improving performance and scaling your industrial data infrastructure. With 64-bit hardware and operating systems now standard, it's no surprise that more organizations are considering this upgrade. However, successful migration involves much more than simply swapping out binaries. Let's break down the key considerations and a recommended path based on current community wisdom and official documentation.

Why Migrate to 64-bit?

There are several compelling reasons:

• Scalability: 64-bit PI Servers can handle much larger point counts and memory requirements, which is especially vital as data volumes grow.
• Performance: 64-bit architecture enables more efficient processing and system reliability.
• Futureproofing: OSIsoft (now AVEVA) and most enterprise IT providers are prioritizing 64-bit support and enhancements.

Is Migration Complex? Compatible? Risky?

Good news: According to field experience and feedback from OSIsoft, PI Server configuration and data files are fully compatible between 32-bit and 64-bit architectures. There’s no risk of corrupting your tag database or losing PI Points simply because of an architecture mismatch. That said, migration isn’t a simple in-place upgrade.

Recommended Migration Approach

1. Perform a Clean 64-bit Installation

   • Set up a new machine (or a new drive on the same machine) with 64-bit Windows and install the latest 64-bit PI Server package. Do not attempt to upgrade an in-place 32-bit PI Server installation to 64-bit—this isn’t supported and typically leads to problems.

2. Backup and Copy PI Data and Configuration

   • Follow the step-by-step instructions in the “Moving PI Servers” chapter from the PI System Server Management Guide. This guide describes in detail which files and configurations need to be carried over. Note: the legacy PISysID.dat file has been replaced by piserver.dat (standalone) or picollective.dat (collective) in recent versions.

3. Restore PI Files on the New Server

   • Restore all relevant configuration, archive, and log files as per the guide’s instructions.

4. Check Component Compatibility

   • Important: Some PI System components (e.g., certain interfaces, RtWebParts, Managed PI) may only have 32-bit versions or limited 64-bit support.
     • If you are using Managed PI, you must install the 32-bit PI Server even on 64-bit hardware or OS. As of now, Managed PI does not support the 64-bit PI Server package.
     • For web-based components, double-check compatibility; for example, RtWebParts may require a 32-bit environment.

What About Interfaces?

Most PI Interfaces (the data connectors) remain 32-bit, but they run fine under Windows' 32-bit compatibility mode (WOW64) on 64-bit systems. This typically doesn’t create issues during migration, but always consult the latest compatibility matrix.

Real-World Experience and What’s Most Common

Migration to a 64-bit PI Server is rapidly becoming the norm, especially for systems with high tag counts—500,000 or more. If your current system is approaching performance limits, scaling up is a must. That said, every deployment is unique. If your organization uses niche PI components or custom integrations, consult documentation and engage with OSIsoft/AVEVA Support before making the leap.

Key Takeaways

• Do not upgrade in-place from 32-bit to 64-bit. Always perform a clean 64-bit install, then migrate the data and configuration.
• Confirm all product and component compatibility, especially for interfaces and legacy web components like Managed PI or RtWebParts.
• Plan, test, and verify at every migration stage to minimize downtime and risk.

By following these guidelines, you can take full advantage of what modern 64-bit PI System infrastructure has to offer—while avoiding common pitfalls along the way.

Further Reading:

• PI System Server Management Guide
• KB Article #3272OSI8
• Community forums and recent case studies on large-scale migrations.

If you've completed a migration or run into unique challenges, share your experience in the comments below!