Airtable Renewal Date and Export Checklist for Owner Change

Open your Airtable billing page and write down the next renewal date, plan, seat count, and payment method. Bending Spoons, the company that lists Evernote, WeTransfer, Vimeo, and Harvest among its main businesses, agreed to buy all of Airtable in an all-cash deal with an enterprise value of $1.285 billion and an implied equity value of about $2.25 billion.

Airtable was valued at $11.7 billion in December 2021 after a $735 million funding round. The deal is expected to close later in 2026, subject to regulatory approvals and other customary conditions. The two-check portability rule: confirm the renewal date and plan, then export the customer, deal, and hiring bases before any owner-driven optimization.

Confirm the renewal date before the deadline

Ownership changes rarely announce themselves with a migration notice. They show up as changes to pricing, access, or plan terms. Unknown billing cycles leave you without the deadline that matters. The renewal date tells you how much time you have before a change can affect the team.

Bending Spoons has described its acquisition model as making substantial changes and continuous improvements to acquired digital businesses to increase earnings. For a small team, the platform may improve, but the team may also face changes before it is ready.

A renewal date without a named owner is just a number. The billing details tell you whether you have days or months. For a founder card, find out who can see the invoice. For a finance-team workspace, ask for the next invoice date in writing.

A distant renewal still needs the export scheduled now and put on the ops calendar. A close renewal needs the export done before the next all-hands. Put the expected close date and the renewal date in the same ops calendar. The close date is context. The renewal date is the deadline. A change in ownership can arrive before the next billing cycle. You do not want to discover the gap while the team is already working around a new interface.

Export the bases you cannot rebuild

Use a rebuild test: treat any base that would be painful to rebuild from memory as the operational record. Customer lists, deal stages, hiring pipelines, weekly ops trackers, and vendor contacts all fall into this category. You do not need to export everything. You need to export the parts that would hurt if they disappeared.

Do not try to export every view, every dashboard, and every experimental table. Those are nice to have, but they are not the company. The records that matter answer questions without a meeting. Who is the customer? What stage is the deal? Who is the candidate? What was promised in the last meeting?

Before you export, check what the file actually contains. A spreadsheet can look complete while missing linked records, formula outputs, or the field names your team uses every day. When the export is incomplete, note the gap and decide whether you need another file, a screenshot of the view, or a short memo describing the structure.

• Open billing and note the next renewal date, plan, seat count, and payment method.
• List every base that holds customers, deals, hiring, or weekly ops. These are the records you cannot rebuild from memory.
• Export each base as a spreadsheet, and check that linked tables are included. A file you cannot read is not a backup.
• Save exports in a shared drive folder with the date and base name. A portable copy should not live only in the workspace.
• Ask a teammate to open a random export and confirm the fields are readable. Verification takes less time than a rebuild.
• Write down the owner, admin, and billing contact for the workspace. Access questions need a named person, not a guess.

A small company should keep a copy the team can open, read, and import when the migration starts.

Keep the copy outside the workspace

Workspace access can change without a meeting. An admin role can be reassigned, a billing card can be replaced, or a base can be moved into a new structure. A tabular file in a shared drive is unaffected by any of that. Portability means the file stays readable, searchable, and importable into another system.

A portable copy should be readable by someone who does not have access to the original workspace. Use a shared drive, a named folder, and a file name that tells you what is inside. When the only person who can open the export is the person who made it, the export is a file with a secret.

Set the trigger in the ops calendar: if plan terms change, start the migration before the next billing cycle.