Skip to main content

​
From another scheduler (Buffer, Hootsuite, Postiz)

  1. Connect your channels - follow the Channels guides. OAuth platforms need credentials configured on your instance; token-based platforms connect directly.
  2. Export your content - export scheduled posts from your current tool as CSV (content + channels + datetime).
  3. Import into PostSider - use CSV import. The generated template matches your organization’s real channel names; the first_comment and thread columns are optional.
  4. Set up posting times - configure per-channel slots under Settings → Queue Plan so queue scheduling uses your rhythm.
  5. Verify with a test publish - publish a draft or a post one minute ahead to confirm each channel works.
  6. Recreate approval and tags - set up the approval workflow if you used one, and re-create tags via the API.

​
Between OSS versions

Self-hosted upgrades are handled per release in Self-Hosting. In short: back up both databases, media, and .env; check the release notes; build the new tag; let migrations run; verify health.

​
From PostSider Cloud to self-hosted (or vice versa)

The application is a single build; only the configuration differs. Export your content with the public API (GET /public/v1/posts in a date range), connect the same channels on the target instance, and re-import with CSV. Media must be re-uploaded or mirrored from the source bucket. API keys, webhooks, and approval states do not carry over.