The Automation Sequence: What a 100-Year-Old Company Learned About Modernization Order

Most companies rushing into AI and automation overlook a fundamental truth: you cannot automate chaos. This becomes painfully clear in industries built on paper processes, where the promise of artificial intelligence collides with the reality of manual handoffs, legacy systems, and disconnected data.

Nate Moeller leads innovation and data at a century-old moving and storage company. His journey from driving trucks to managing a legacy ERP migration reveals why the sequence of modernization matters more than the technology itself.

Why Starting with AI Skips the Foundation: The Digital Transformation Reality

The transportation and storage industry still operates on paper. Drivers leave the warehouse with physical folders. Supervisors audit physical documents. Billing departments process physical paperwork. This is not unique to one company. It is endemic to the sector.

The instinct is to jump to artificial intelligence. Vendors pitch AI solutions daily. Executives want to announce AI implementation. But AI cannot fix what digital processes have not yet replaced.

"We talk about data handoffs," Moeller explains in our podcast episode, 54 Systems, 14 Processes: The Cost of Poor Systems. " The reason we call them that is because you literally hand the piece of paper from somebody to somebody else."

The goal is not eliminating people. The goal is eliminating the manual transfer of information between systems and departments. That requires digital infrastructure first. Automation second. AI third.

This sequencing applies across industries undergoing paper to digital transformation. Manufacturing, healthcare, logistics, and professional services all face the same challenge. The foundation must be digital before intelligence can be layered on top.

Measuring What Matters: How One Metric Revealed System Failure

Three years ago, one metric exposed the cost of fragmented systems: delivery to invoice time averaged 42 days.

For an asset-heavy business with millions in warehouse space and hundreds of vehicles, this created a cash crisis. Add net-30 payment terms and the company waited 72 days from job completion to payment. Growth becomes nearly impossible under those conditions.

The metric served as a North Star. It quantified inefficiency. It justified investment. It measured progress.

Within three years, delivery to invoice dropped to 20 days. The improvement came not from new technology but from understanding where processes broke down and fixing the handoffs between systems.

Organizations planning a legacy ERP migration often lack this baseline metric. They know systems are broken. They cannot quantify how broken or where to focus first. Establishing one clear measure of process efficiency provides both justification and direction.

For distribution and fulfillment operations processing hundreds of daily transactions, even shorter cycles matter. But the principle holds: measure the process end-to-end before selecting technology to improve it.

The Three-Phase Approach: Audit, Consolidate, Migrate

A systems audit uncovered 54 different applications running across business lines. Twenty-five performed core ERP functions. This proliferation happened because the legacy system could not adapt to new business models.

When business units cannot get what they need from corporate systems, they find workarounds. Cloud applications with monthly subscriptions make this easier than ever. IT says no. Business units subscribe anyway.

The result is data fragmentation, security gaps, and process chaos masked by departmental efficiency.

The path forward requires three phases executed in order:

First, audit every system. Understand what each does and why it exists. Most organizations lack this complete picture. Some systems persist simply because no one remembers canceling them.

Second, consolidate processes before consolidating systems. Eight business verticals operated 14 different core workflows. All moved items from point A to point B. The workflows differed in minor details that became major obstacles to standardization.

Process consolidation forces difficult conversations. Every department believes their requirements are unique. When everyone is special, no one is special. Getting stakeholders to think at the enterprise level rather than the departmental level determines success or failure.

Third, migrate to systems that support the consolidated process. Not before. Migrating fragmented processes to new technology simply creates expensive fragmentation.

Research from Gartner on ERP modernization confirms this sequence. Organizations that standardize processes before selecting systems report higher satisfaction and faster time to value.

Eliminating Data Handoffs Before Adding Intelligence

The opportunity for automation lives in the handoffs. Every time information transfers from one person to another, one system to another, or one format to another, friction exists.

Paper to digital. Email to spreadsheet. Phone call to database entry. These transitions consume time, introduce errors, and delay cash flow.

Automation eliminates handoffs. It does not replace people. It removes the manual work of moving information between steps.

This distinction matters for workforce adoption. Employees resist technology that threatens jobs. They embrace technology that removes tedious tasks.

The company found one clear automation opportunity during process mapping. Success there created executive excitement and user acceptance. It demonstrated value before the larger ERP migration.

Starting with quick wins builds organizational confidence. It develops internal expertise. It proves the approach works before betting everything on a multi-year implementation.

For companies exploring transportation industry digital transformation, the lesson is clear: automate specific handoffs first, then scale to broader process automation.

Setting Realistic Timelines: From 20-Year-Old Code to Modern Infrastructure

The existing ERP runs on code written 20 years ago. It still works well for the original business model. It performs admirably for the core moving and storage operation. Delivery to invoice for that legacy workflow sits at six days.

The problem is not performance. The problem is flexibility. The system was locked down for efficiency. No room was left for business evolution. When new opportunities emerged, the system could not adapt.

This created a critical lesson for the next implementation: build in flexibility from the start.

An ERP is not a lifetime decision. But it is a long decision. Changing systems every few years destroys value. Planning for a decade or more requires anticipating change without knowing what will change.

The implementation strategy reflects this reality. The new ERP will not be monolithic. Salesforce handles CRM. A specialized WMS manages warehouse operations. Field service software supports mobile workers.

The ERP becomes the hub, not the universe. Integration matters more than comprehensiveness.

This modular approach provides flexibility. Individual components can be upgraded or replaced without replacing everything. But it requires strong integration architecture and data governance.

Timeline expectations remain realistic. Process consolidation in 2025. Vendor selection and onboarding in early 2026. Implementation extending into 2027 and beyond.

This is not fast. It is thorough. For a company built on 100 years of process evolution, moving deliberately beats moving quickly.

The risk of poor ERP implementation is not just wasted money. It is organizational disruption that damages customer relationships and employee morale. Getting the sequence right matters more than getting it done quickly.

Organizations facing similar transitions should expect 18 to 24 months minimum for meaningful progress. Vendors who promise faster timelines are either oversimplifying scope or setting up disappointment.

The path from legacy systems to modern infrastructure is not a technology project. It is a business transformation that happens to involve technology. It requires process discipline before platform selection. It demands measuring current state before imagining future state. And it insists on eliminating manual handoffs before adding artificial intelligence.

Companies that respect this sequence build sustainable competitive advantage. Companies that skip steps build expensive technical debt.

---

Connecting with senior business and technology leaders to discuss how companies are modernizing their tech stack - whether that's scaling beyond legacy systems or adopting cutting edge AI tech. Tune in to 'Shift Happens' with Blair Hicken. Available in Spotify and Youtube.