NetSuite OpenAir to SuiteProjects Pro: What Changed
What the rename actually means for your team, and what doesn't change at all.
If you've worked with OpenAir for any length of time, you've probably noticed the name shift to SuiteProjects Pro and wondered what it actually means for your team. I hear this question from clients regularly enough that it's worth answering directly.
The short version
SuiteProjects Pro is OpenAir. Same core platform, same underlying data model, same fundamental approach to managing projects, resourcing, time and expense, billing, and revenue recognition. Oracle renamed it as part of pulling it more tightly into the broader NetSuite "Suite" branding family, alongside continued product investment. If your organization is on OpenAir today, nothing about your existing setup breaks or requires urgent action because of the name change alone.
SuiteProjects Pro is OpenAir. Same core platform, same underlying data model, same fundamental approach.
What's actually different
The rename came with ongoing product development, the kind any active platform gets over time, not a wholesale rebuild. What you'll notice varies by how closely you follow release notes, but the changes tend to show up as incremental UI updates, expanded reporting options, and continued integration work with the rest of the NetSuite ecosystem. None of it changes the core implementation, configuration, or UAT approach that's worked for OpenAir for years.
What this means for your team
A few practical things worth knowing:
Your contracts, documentation, and internal references to "OpenAir" don't need an urgent rewrite. Update them at a natural point, like your next contract renewal or a documentation refresh, not as an emergency.
Your team members searching for help or training material should search both terms. A lot of existing documentation, forum posts, and community knowledge still uses "OpenAir," and that's going to be true for a while yet.
If you're evaluating the platform for the first time, you're evaluating SuiteProjects Pro, full stop, there's no separate "OpenAir version" to compare against.
Where the confusion actually causes problems
The real risk isn't technical, it's communication. I've seen teams lose time in vendor conversations, RFPs, and internal planning because someone assumed "SuiteProjects Pro" was a different, newer product requiring a fresh evaluation, when it's the same platform they already know.
If you're mid-implementation or mid-optimization and this naming shift is creating confusion internally, that's worth clearing up early rather than letting it complicate decisions that don't actually need to be reopened.
If your team has questions about what the rename means for your specific setup, get in touch.
Get the next one in your inbox.
PS Playbook is a weekly(ish) read for Professional Services teams who want their operations to actually work.
