After the Cloud migration: cleaning up what the move left behind
The cutover went well. Then the administrators find (migrated) everywhere: duplicate schemes, roles and screens, and notes under every field. Why the duplicates exist, how to consolidate them safely, and how to keep the new site from drifting back into the old one.
Moving off Smartsheet to Jira and Confluence: what lands where
Move everything to Jira is the wrong plan. A Smartsheet estate is many kinds of things wearing the same grid. How to sort sheets by what they really are, migrate only the live ones, use templates instead of one-offs, and handle the formulas, automations and forms that never move on their own.
When one custom Forge app beats three Marketplace subscriptions
Marketplace apps are priced on your whole site's user count, so an app bought for one team is paid for everyone. When replacing several of them with one small custom Forge app makes sense, what it costs you instead, and when to keep buying.
Finding the Atlassian licenses you pay for and nobody uses
Atlassian Cloud bills for every account with product access, whether or not the person logged in this year, and your Marketplace apps follow the same user count. How to find the inactive accounts, sort them before removing anyone, and make reclamation a habit rather than a yearly project.
Sizing a ScriptRunner migration to Cloud before you commit to a date
ScriptRunner is usually the hardest app in a Jira migration, and its estimates go wrong in both directions. How to build a matrix of every script, drop what is dead, collapse the duplicates, translate a first draft to see the real difficulty, and present two honest numbers.
The Confluence macros that do not survive the move to Cloud
In a Confluence migration the pages move fine. The macros inside them are what break. How to count them, sort them into three groups, find the nested ones, and decide what to rebuild before content owners discover the gaps for you.
What a Jira Data Center to Cloud assessment should actually tell you
A migration assessment is not a list of installed apps. It is a decision for every app, a measured cleanup, and an effort number you can defend in a meeting. Here is the shape we use, and why each part of it exists.