Succession planning for family-owned distributors: data and systems checklist

Why data and systems belong in a succession plan#

Data and systems belong in a distributor succession plan because the business often runs on access and knowledge concentrated in one or two people. The founder may be the only ERP administrator, the only person who knows why a contractor gets special pricing, and the keeper of the supplier rebate relationships.

Attorneys and accountants handle ownership transfer, and leadership development handles the people side. The data and systems checklist covers the practical layer in between: making sure the next leader can run the systems, find the records and understand the decisions behind them from the first day.

System access checklist#

A system access checklist confirms who controls each system and removes any dependence on a single person. Work through it with the IT provider or office manager, and keep the answers in a company password manager or a sealed document the next leader can reach.

Who actually owns the records?#

Business records should belong to the operating company, but in a family business they are often scattered. Records may be split across the operating company, a real estate entity that owns the warehouse, a separate trucking company and the founder personally, and supplier negotiations may have run through a personal email address for decades.

• 1Confirm which legal entity holds each system subscription and software license.
• 2Move business email and files off personal accounts and personal devices.
• 3Identify records held by entities from past mergers, reorganizations or closed branches.
• 4List paper records still in storage, such as signed credit applications, supplier agreements and older customer files.
• 5Note records kept by outside parties, such as the accountant, the IT provider or a former partner.

Document the decisions, not just the data#

Documenting key decisions means recording the reasons behind numbers already sitting in the ERP. The ERP shows a contractor's special price level; it rarely shows that the price was agreed to win a hospital project, or that a credit limit was raised because the founder had known the customer's family for years.

Short recorded conversations or written notes with the founder are usually enough. The format matters less than capturing the reasons while the person who made the decisions can still explain them.

• 1Pricing: customer-specific price levels, matrix rules and the reasoning behind exceptions.
• 2Credit: how limits are set, who receives terms and how past collection problems were handled.
• 3Suppliers: rebate agreements, territory understandings, line card decisions and the people behind them.
• 4Customers: accounts with special handling, standing service commitments and history worth knowing.
• 5Inventory: stocking choices for slow movers, special-order policies and past obsolescence write-offs.

Illustrative: a second-generation PVF distributor plans the handoff#

Illustrative: a fictional plumbing and PVF distributor with three branches is preparing to pass leadership from the founder to a daughter who runs one of the branches. The company uses Infor for orders and inventory, a hosted email tenant and an EDI provider for two large mechanical contractor customers.

The review finds that the founder is the only ERP administrator, supplier rebate correspondence lives in his personal email, and the warehouse belongs to a family real estate entity whose records are mixed into the operating company's files. Over the following months the company adds the controller as a second administrator, moves supplier email to company accounts, separates the real estate records, and records a series of sessions in which the founder walks through pricing exceptions and key supplier relationships. The daughter takes over with access, records and context already in place.

Mistakes that make the handoff harder#

The most common mistake is treating systems as an IT detail to sort out after the leadership decision. By then the founder may be less available, and simple fixes such as a second ERP administrator turn into urgent requests to a software vendor's support desk.

Other mistakes are quieter. Families sometimes clean up the ERP by deleting old customers, closed branches or inactive items, which removes history the next leader will want for pricing and purchasing. Others let an outgoing bookkeeper or IT contractor leave without a handover, taking undocumented reports and EDI mappings with them.

• 1Deleting historical customers, items or branches to tidy the ERP before the handoff.
• 2Letting departing staff leave without handing over reports, scripts and passwords.
• 3Keeping supplier agreements only in the founder's files or inbox.
• 4Assuming the IT provider holds admin rights on the company's behalf without checking the contract.

What the next generation should know about the records#

The next leader should know what records the company holds, how far back they go and how they support the business. Long order histories, quote-to-order records, returns and counter notes feed pricing, purchasing and customer decisions, and they are the raw material for any AI tools the company adopts.

Some established distributors also consider whether those records could be licensed. That is optional and separate from succession, but the same inventory serves both purposes. The SourceX Enterprise Data Value Framework rates records on drivers such as uniqueness, domain expertise, human-generated signal, scale, recency, data cleanliness, rights and AI utility, while preparation cost and privacy burden reduce net value. Decades of quotes, orders and exception notes kept in one system, with clear company ownership, rate better on rights and cleanliness than the same history scattered across personal inboxes.

How SourceX can help during a transition#

SourceX helps established companies license operational records through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The first fit check uses metadata only, such as system names, years of history and record families, so it can run alongside succession work without moving any files.

For a family business the most useful step is often the inventory itself. Whether or not a license follows, knowing which records exist, which entity owns them and who can approve their use makes the handoff cleaner and any later sale easier.