What you can actually export before a social tool shuts down

A shutdown notice, or an acquisition notice that reads like one, leaves a team with years of content, captions and performance data sitting in somebody else’s database. There is an export button, and it usually does not cover everything. Completeness is decided category by category. Here is what to check, and in what order.

The window is shorter than the sunset date says

Treat the published cutoff as a ceiling, not a deadline. It is when the lights go off, not the last day the building is staffed. Once a team shifts toward wind-down, the things an export depends on degrade first: support queues lengthen as the people answering them leave, export jobs on large libraries time out, and API access is often restricted early because it is the cheapest thing to shut off.

So attempt the export the same day you see the notice. An acquisition deserves the same urgency: until the acquirer confirms a migration path in writing, naming which data moves and on what date, it is indistinguishable from a shutdown of the old infrastructure.

What “export your data” usually bundles, and what it usually leaves out

These categories travel separately. Check each against your vendor’s own documentation rather than assuming one export covers the set:

  • Media and content library files. The image and video files at the resolution you uploaded, not thumbnails and not links.
  • Post captions and published history. Text, hashtags, links, timestamps, and which account each post went to.
  • The scheduling queue. Posts drafted, approved or queued but not yet published. Stored separately from published history, and often exported separately too.
  • Historical analytics. Reach, engagement and click data, especially for periods older than the connected platform’s own retention.
  • Audience or follower lists, only where the source platform’s terms permit any export at all.
  • Team members and permission structures. Who had which role, on which accounts.
  • Connected accounts and API tokens. Which integrations were authorised, and what they still reach after you stop paying.
  • Automation and approval rules. Queue schedules, category rules, approval chains, recycling settings.

Whether a category is included is stated, if at all, in that vendor’s own export documentation or export dialog. It cannot be inferred from another tool.

The two ways an export commonly falls short

The first pattern: well structured for text and metadata, thin on media. Agorapulse documents this boundary for its calendar CSV. Its help article states that “The export includes Publishing information only. Analytics and Inbox data are not included in the export,” and the listed fields include scheduled date, scheduled time, post status, post content, image URL and video URL. Those last two are URLs, not files, and the same article notes the CSV cannot be used to bulk import posts back in. A file of links to media hosted on infrastructure about to be decommissioned is not an archive.

The second pattern runs the other way: a clean download of every original file, with nothing that reconstructs the queue. Captions detach from their assets, scheduled posts vanish, and approval rules were never in scope. [EVIDENCE NEEDED: a live first-party vendor export document stating that media files are exported while the scheduling queue and workflow rules are not.]

Assume neither pattern describes your tool. Run one small export over a narrow date range and open the result. Confirm a media file downloads at full resolution, and that a post you know is queued appears with its scheduled time attached.

Finding the export function before you need it

Export tooling sits in one of four places.

Sometimes it is inline with the data. Agorapulse’s post export runs from the Month view of the publishing calendar rather than a settings page, so anyone hunting through account settings will not find it. Sometimes it is role gated: the same vendor’s reports documentation states that Owner, Co-owner and Manager roles can export and schedule reports by default, while Advanced Members and Members require Admin or Editor access. If whoever runs your export is not the owner, check today that they are allowed to.

Sometimes the real export is an API on a paid tier. Metricool’s help documentation places API access under Account Settings and states it is available on Advanced and Custom plans.

And sometimes there is no self-serve export at all. File the support request the day the notice appears, in writing, naming the data categories and the format you need. A dated, itemised thread is a record. A phone call is not.

What happens to data after the account closes

There is no standard retention window, and assuming one is how teams lose data they thought was recoverable. Read the retention or deletion language in your vendor’s current terms or privacy policy during the notice period.

Some are explicit that deletion is permanent and total. Buffer’s help documentation for account deletion describes it as permanent, states that it deletes all accounts associated with that email address, and notes that posts already published to your connected social accounts remain in place on those platforms. Its deletion section describes no recovery window once the deletion is confirmed.

Where a vendor falls under a jurisdiction with a data portability right, that is a second route, and it can be invoked as a dated written request. GDPR Article 20 scopes that right to processing based on consent or a contract and carried out by automated means, so confirm it covers your account and your data rather than asserting it.

The 48-hour checklist

  1. Export the media and content library first. It is the largest, the slowest, and the least recoverable elsewhere.
  2. Export post history and captions, and confirm each ties to the correct account and date.
  3. Export or screenshot analytics before you cancel anything, not after.
  4. Export the scheduling queue, then list every queued post that did not come through.
  5. Document team members and permission levels, by screenshot if there is no export.
  6. Record every connected account and integration, and revoke the tokens you no longer want live.
  7. Save the retention or deletion clause from the vendor’s terms, with the date you read it.
  8. File a written support request for every category with no self-serve export.

When the export comes back incomplete

Do this the same day. Send a written support request naming the missing category in the vendor’s own vocabulary, stating what you received and what you expected. Manual exports not exposed in the interface do sometimes exist, and a specific request reaches whoever can run one faster than a general complaint does.

Then archive by hand whatever the export format cannot hold. Dashboard views, approval threads carrying client feedback, and comment histories on in-progress posts are presentation layers, not exportable objects. Screenshot them while you still have a session, and confirm that whoever holds admin access will still hold it next week, the continuity problem behind how teams already handle shared account access.

Before you close the tab

Two related pieces are worth reading next: a convention built to survive a handoff, and what these tools actually record versus what they let you take with you.

Vendor documentation cited here was verified on 5 September 2026 against the vendors’ own help pages, listed below. This is not Watchdog data and is not on the re-verification schedule, so confirm any detail against the vendor’s current page. followedapp is published by the team behind RecurPost, and RecurPost is covered under the same rules as every other vendor.

FAQ

How much notice do vendors typically give before a shutdown?

There is no standard. Notice periods are set per vendor and run from immediate account closure to a long wind-down. Treat whatever notice you received as the outer edge of your window, not a safe deadline.

Does an export include scheduled but unpublished posts?

Sometimes, and it is one of the categories most often dropped, because a scheduling queue is usually stored separately from published history. Verify it for your own tool. Run a test export over a future date range and check whether queued posts arrive with their scheduled times.

Can I get my analytics history after cancelling my account?

Often not. Historical analytics usually depends on the tool holding live API access to your connected platforms, so it is among the first things to stop working once you cancel. Export or screenshot the reporting you need before initiating cancellation, not afterwards.

What happens to my data if the vendor is acquired rather than shut down?

It can go either way. The product may continue under new ownership with a real migration, or the acquisition may function as a shutdown of the old infrastructure. Until the acquirer confirms the migration plan in writing, treat the notice exactly as you would a shutdown.

Is there a legal right to get my data back from a vendor?

It depends on jurisdiction. GDPR Article 20 establishes a right to receive personal data you provided to a controller “in a structured, commonly used and machine-readable format” and to transmit it elsewhere, where processing rests on consent or a contract and is automated. [EVIDENCE NEEDED: the equivalent statutory portability right, if any, outside the EU.]

Sources

Scroll to Top