Packaging Technology Due Diligence: What to Check Before You Sign

packaging business systems technology due diligence

Before a packaging acquisition closes, the buyer will have walked the plant floor, inspected the corrugator or presses, reviewed three years of financials, read the customer contracts, and checked the environmental permits. But have they asked how a quote gets built, where the job costs live, or what happens to the schedule when the one person who understands the system takes a vacation?

That gap is where integration plans go wrong. A corrugated executive we spoke with, months after closing on a new plant, put it this way: “We’re looking at their systems right now trying to figure out: what can we extract? What data do we need to create the information we want?” Those are good questions. They are also questions that should have been answered before signing.

Use the checklist below to establish what the target runs, whether its data can be trusted, and what integration will take.

Why systems get skipped

Three things push technology to the bottom of the diligence list.

The first is speed. Diligence windows are short, access is limited, and the seller controls what you see. The financial and legal workstreams have to happen; everything else competes for the time left over.

The second is access. The seller’s IT, if there is a dedicated person at all, is often one individual who is also running the network and the phones. Asking detailed questions about data structures can feel intrusive, and sellers worry that it signals a plan to change things their staff are attached to.

The third is the assumption that systems are a post-close problem. The logic goes: we are buying the plant, the customers, and the people; whatever software they use, we can sort it out later. Later is where the previous post in this series happens. Five acquisitions in, the systems are still separate, and someone is compiling the sales report by hand.

What the research says

In McKinsey’s 2019 research, respondents said more than 40% of their deals suffered from inadequate due diligence. The lesson is to assess what it will take to run the business, alongside what it will cost.

PwC’s 2026 survey found that 59% of successful acquirers had turned value drivers into executable initiatives before integration, versus 28% of limited-success acquirers. The overall figure was 46%. The survey covers businesses with at least $1 billion in revenue; it supports early planning, rather than predicting a converter’s outcome.

For a packaging acquirer, that means deciding how the combined operation will work, then choosing the systems and integration plan to support it.

The checklist

Start with five areas. A session with the target’s operations lead and systems owner can identify the gaps. Validate the answers with sample data, contracts and recovery records; use specialist diligence where the risks require it.

1. Systems: what runs the business

  • What system handles estimating and quoting? Scheduling? Inventory? Shipping? Finance? Is it one platform or several?
  • Who is the vendor, what version is installed, and when was it last upgraded? Is it still supported?
  • Is the ERP hosted in the cloud or on site? Who manages updates, backups and recovery? Can users at a new plant be added without installing another ERP server, and what connectivity or local interfaces will they need?
  • Is any of it homegrown, built on spreadsheets or Access, or dependent on one contractor? Who supports it if that person leaves?
  • What runs on the plant floor: machine interfaces, shop-floor data collection, quality systems? How do they connect to the MIS, if at all?

 

2. Data: what you are actually buying

  • How are customers, products, and specs coded? Will they map to yours, or will every record need to be rebuilt?
  • Are cost standards (machine rates, waste factors, labor) maintained, and how recently? Do actuals get captured against them?
  • Can they produce job-level profitability for the last twelve months? If it needs to be reconstructed, establish how long that will take and whether the result can be reconciled to the accounts.
  • Where does the data live, who controls access, and can you obtain a usable export? Ask for a sample, including specifications and attachments. Check software licenses, support agreements and any change-of-control or transfer conditions with the deal’s advisers.

 

3. People: who holds the knowledge

  • How many people can operate each system? How many can configure or fix it?
  • Is there one person the whole operation depends on? What do they know, is it documented, and are they willing and able to support the transition
  • Who built the current quoting logic, and is it documented anywhere?

 

4. Processes: how work actually flows

  • Walk one order from inquiry to invoice. Where does it leave the system and go to paper, email, or a whiteboard?
  • How are changes to a job in progress handled? How is waste recorded? How is month-end closed?
  • What reports does management use, and how are they produced? Also ask who can access the business and machine networks, how remote access is controlled, and when backups were last restored successfully. NIST’s 2026 OT Backup Quick Start Guide emphasizes regular backups, testing and recovery exercises for manufacturing systems.

 

5. Migration: what it would take to bring them onto your platform

  • Given the answers above, is this a data migration, a re-implementation, or a rebuild?
  • What is the realistic timeline, who from the target would need to be involved, and what is the cost?
  • What disruption could the transition cause, and when is the safest production window? Define how orders, work in progress, stock and receivables will be reconciled at cutover, and how the plant would recover if go-live failed.

 

The answers do two jobs. They tell you how much integration work you are buying, which belongs in the price. And they tell you where the risk sits, which belongs in the plan.

Red flags and green flags

Some findings should change the price or the plan. Others should reassure you.

Red flags

  • Quoting lives in one person’s spreadsheet, and that person is the owner who is selling.
  • Cost standards have not been updated in years, so quoted job margins may not reflect current production costs.
  • The MIS is unsupported, on an obsolete version, or dependent on undocumented customizations.
  • Nobody can produce job-level profitability without a project.
  • Shop-floor data is collected on paper and keyed in later, or not at all.
  • Customer and product master data is inconsistent enough that the sales team keeps their own lists.

 

Green flags

  • The target runs a current, supported MIS, ideally the same one you do. A corrugated executive told us plainly why that matters: “We like buying companies that are already on Amtech because it makes integration a lot easier.”
  • A supported cloud ERP with clear responsibility for updates, tested recovery and a practical way to add sites. Check that the functions the group needs are available in the proposed deployment.
  • Standards are maintained, actuals are captured, and management routinely reviews job profitability.
  • More than one person can run and configure the system, and the processes are documented.
  • A sample data export is complete, readable and reconciles to the target’s records. Recovery procedures have also been tested.

 

A target with green flags is not just easier to integrate. It is easier to value, because the numbers you are paying for can be traced to real jobs. That is why post 5 in this series argues the same checklist is worth running on your own business if you ever plan to sell.

From findings to a plan, before close

Technology diligence should produce three decisions, documented before signing wherever access allows.

First, the target platform. Will the acquired plant move onto the group’s system, stay on its own, or be connected through a reporting layer? The previous post in this series covers the trade-offs; the point here is that the decision should be made with the diligence findings in hand, not twelve months after close when the pain has become obvious.

Second, the migration scope and timeline. Set the scope from the evidence: data cleanup, interfaces, machine connections, testing and training. Agree on an owner, a production window and go-live criteria. The date should reflect the work required, even when both businesses use the same software.

Third, the people plan. If one person holds critical knowledge, agree how it will be documented and transferred, who needs to stay through the transition, and how their time will be covered.

The technology leader at a private-equity-backed label group described the payoff when this is done well: “When we get back into growth mode, that’s the payoff of all of this.” A group that already knows what it will do with the next plant’s systems before it buys the plant can move faster than one still figuring it out from the last deal.

Next in the series

The next post takes the speed argument head-on: what a single multi-plant platform does to the integration timeline, and why converters are starting to treat M&A speed as a measurable payoff from their technology investment.

Have a deal in progress?

Talk to us about the systems, data and migration questions to resolve before you sign.

Other posts in the series

  1. Packaging M&A in 2026: Faster Integration Is the New Edge
  2. The hidden cost of running multiple ERP or MIS instances, and what “we haven’t touched it” actually costs over five acquisitions.
  3. Technology due diligence: what to look at in a target’s systems before you sign.
  4. M&A speed as the payoff: how a single multi-plant platform changes the integration timeline.
  5. Becoming acquisition-ready: what sellers can do now to look like a low-risk target in a selective market.
 

Sources

  • McKinsey: Eight basic beliefs about capturing value in a merger (April 2, 2019; survey respondents reporting inadequate diligence). https://www.mckinsey.com/capabilities/people-and-organization/our-insights/eight-basic-beliefs-about-capturing-value-in-a-merger
  • PwC: 2026 M&A Integration Survey (September 29, 2026; executable initiatives: 46% overall, 59% successful, 28% limited-success acquirers). https://www.pwc.com/us/en/services/consulting/deals/library/ma-integration-survey.html
  • NIST: OT Backup Quick Start Guide, SP 1339 (June 17, 2026; regular backups, testing and recovery exercises for operational technology). https://www.nist.gov/publications/ot-backup-quick-start-guide
  • Amtech: Cloud Hosting (managed infrastructure and adding plants without additional ERP servers). https://www.amtechsoftware.com/services/cloud-hosting/