Minneapolis agency work meant a new scale of animal: enterprise Drupal portfolios, as sole technical lead. Sites with histories longer than some careers, content in the millions of records, organizations where the website wasn’t the brochure — it was load-bearing infrastructure with departments leaning on it.

The first discovery was how much doesn’t change with scale. An enterprise Drupal estate and a Fargo small-business site fail identically — ownership fog, deferred updates, the one person who understood everything moving on — just with more zeroes attached. Big organizations don’t avoid the abandoned-website pattern; they run it with better letterhead. I stopped being surprised by that within the first year, and it’s why this practice now says nobody should lose a website without qualifying by size. The disease doesn’t check revenue.

What does change at scale is the cost of being casual. On a small site, an untested change bites you and you apologize to one owner. On an estate, casualness compounds across millions of records and thousands of daily users, and “oops” becomes a meeting with a very long table. The migration years are where my methods calcified from habits into rules — the counting, the increments, the rehearsals — because at that scale, rules are the only thing that scales with you. The portage method got its shape here, even if it got its name by a lake much later.

And this era rewired my relationship with Drupal itself. I’d built on it since the D7 prime; now I was living inside its deepest machinery — the migrate system, entity storage, the plumbing under the floorboards — daily, at volume. There’s a difference between knowing a platform and knowing where it creaks. The second kind of knowing is the one clients are actually buying when they hire a migration lead, and there’s only one way to acquire it: tonnage.

The tonnage was about to arrive.

Next: Millions of nodes — the big one.