How to Build a Software Vendor Shutdown Plan After the Botkeeper and Affixa Closures

A software vendor shutdown plan is a short written checklist that says where your data lives, how to export it, and what tool would replace the product. Build it before you need it. Botkeeper and Affixa both announced closures in 2026, and customers with an export routine had the easiest time.

This guide is for owners and office managers who rely on small software vendors for bookkeeping, email, payroll or time tracking. It shows how to rank your tools by risk, schedule exports, and write a one-page exit plan. Little iApps tests business software for cost and fit, and vendor stability is part of that cost.

What the 2026 shutdowns show

Botkeeper, an AI bookkeeping vendor that had raised nearly $90 million, announced on February 9, 2026 that it was closing, according to CPA Practice Advisor. Less than three weeks later, Xendoo announced it had bought the Infinite platform and said access would stay active.

That ending was lucky. Customers had no way to know it was coming when the closure notice arrived. Those who had already exported their books spent the next weeks deciding, not scrambling.

Affixa is a smaller case. The vendor of a Windows email tool announced on January 16, 2026 that it would sunset the product. Its retirement notice says renewals stop on January 1, 2027, all services cease on January 31, 2027, and server data is deleted on February 1, 2027.

The two cases have one thing in common. Neither vendor was a household name, and neither customer base was told far in advance. A small team's tools often come from small vendors, so the risk is not rare.

Which of your tools carry the most risk?

Rank each tool on two scores: how much your business depends on it, and how likely the vendor is to disappear or change terms. Tools that score high on both need an exit plan first. Examples include accounting add-ons, payroll tools and customer databases.

Start with a list of every paid tool and its monthly cost. Include the free ones that hold business data. Then add four columns: what data it holds, who owns the account, how the data can be exported, and when it renews.

Signs of higher vendor risk include a small team, a single founder, recent layoffs, a pending sale, a sudden price jump or a product that depends on another company's platform. Affixa, for example, depended on a Microsoft email subsystem that Microsoft plans to retire.

A big vendor can also change terms. Our post on the Harvest price increase shows how an ownership change can raise bills with the same product. Price shocks and shutdowns call for the same preparation.

How to set up a regular export routine

Pick an export schedule for each critical tool and put it on the calendar. Monthly works for accounting and customer data. Quarterly is enough for lower-risk tools. Save the files to a cloud folder and a second location that you control.

The U.S. Small Business Administration (SBA) advises on its page on managing your finances that you should back up data on all computers regularly, ideally to cloud storage weekly, and it lists financial and accounting files as critical. Use that as your minimum for any tool that holds money records.

Format matters more than frequency. Prefer open formats such as CSV, PDF and plain text over a vendor's own file type. A CSV of customers can load into almost any replacement, while a proprietary backup may only restore into the product that just closed.

Test one export each quarter. Open the file, check that the row counts match, and try importing a sample into a free tool. An export you have never opened is a hope, not a backup.

What should a one-page exit plan include?

A one-page exit plan names the tool, its owner, the data it holds, the export method, a chosen replacement and a deadline for switching. Keep it short enough that a manager can follow it in a crisis, and store it where more than one person can find it.

Use the same six lines for every critical tool. Tool and owner come first. Then list the data type and where the export is saved. Then name the replacement, how long a switch would take, and who approves the spend.

Choose the replacement before you need it. A short trial of one alternative per critical tool takes a few hours and saves days later. Our guide to switching payroll providers without missing a tax deadline is a good model for planning around fixed dates.

Which records must you keep after a vendor closes?

You must keep records as long as they are needed to prove income or deductions on a tax return. The Internal Revenue Service (IRS) says in its recordkeeping guidance that employment tax records should be kept for at least four years.

That rule is why exports matter. If the only copy of last year's payroll runs sits inside a service that has closed, you may not be able to produce it for an audit. Save payroll reports, invoices, bank feeds and year-end summaries as files you hold.

Payment data deserves special care. Our walkthrough on connecting a payment processor to accounting software before 1099-K season shows how the same transactions flow into your books, which also tells you where the export should come from.

How to react when you get a shutdown notice

Read the notice for three dates: the last day to renew, the last day the service runs, and the day your data is deleted. Affixa's notice listed all three. Put each one on the calendar with a reminder two weeks before.

Export everything the same day. Do not wait for the final month, since support teams get slow and export tools sometimes break near the end. Then ask for a refund if you prepaid past the closing date. Affixa limited refunds to certain multi-year subscribers, so ask early.

Pick the replacement and run it in parallel for one billing cycle. Compare outputs side by side so you can spot a gap before the old tool disappears. For a full migration order, read our post on moving off standalone SharePoint and OneDrive plans, which walks through moving file storage step by step.

Finally, tell the team. Staff who use the tool daily need to know the new tool, the date and who to ask. A short note with a link to the exit plan prevents duplicated work.

A worked example for a ten-person firm

A ten-person services firm might list nine paid tools. Four of them hold money or customer data: accounting software, payroll, a customer database and a time tracker. Those four get the full exit plan. The other five get a line on the list and a yearly check.

For accounting, the firm exports the chart of accounts, the general ledger and the last three years of invoices every month. For payroll, it saves each pay run report and the quarterly tax filings. For the customer database, it exports contacts and notes to CSV.

For each of the four, the owner picks one backup candidate and notes its price. The whole exercise takes an afternoon, and the firm ends with a one-page document per tool. When a vendor emails a closure notice, the response is a calendar item, not a crisis.

The point is that the plan scales down. A solo owner can do it in an hour with three tools. A larger team can assign one tool per manager and review the list at the same yearly meeting where budgets are set.

Questions to ask a vendor before you sign

Ask every new vendor a few direct questions. How can I export all of my data, and in what format? What happens to my data if you close or sell the company? How much notice will I get, and will you refund prepaid time?

A good vendor answers in writing. If the reply is vague, treat that as information. Our post on negotiating a software renewal price increase shows how to ask for terms such as rate locks, and the same approach works for export rights.

A yearly review keeps the plan alive

Set a yearly review for the same week you do budgets. Update the tool list, check each export still works, and drop tools you no longer use. A plan that was right two years ago may now point at a product that has been sold or renamed.

Use the review to ask one more question about each tool: what would we do if the price tripled? The answer often reveals which tools are easy to replace and which have quietly become load-bearing.

Conclusion

A vendor shutdown plan turns a surprise into a project with a date. List your tools, rank the risk, schedule exports in open formats, and name a replacement for every critical one. Keep the records the tax rules require, and review the list once a year.

Your next step is to pick the one tool you could least afford to lose and run a test export this week. Little iApps will keep covering closures, sales and price changes so you know when to update your plan.