# How to Switch from Postiz to DunSocial without Running a Server

> Switch from Postiz to DunSocial with MCP: dump your queue to Markdown, recreate it hosted, test one prompt, then retire the Docker stack you were maintaining.

- Published: 2026-09-25
- Last updated: 2026-09-25
- Author: Sanju (Founder & CEO @ DunSocial)
- Topics: postiz, migration

---

<script>
	import { CodeSnippet } from '$lib/components/content';
</script>

You already live in Claude, ChatGPT, or Cursor. Postiz ships an MCP server, & so does DunSocial. That means you can switch from Postiz to DunSocial without missing a post by treating the move as an agent-to-agent handoff you review: dump the queue to Markdown with Postiz MCP, recreate drafts with DunSocial MCP, test one small prompt, check the calendar the next day, & then retire the server you were maintaining.

This guide is for solo founders & small teams who picked Postiz for its "free & self-hosted" pitch, then found the free part came with a server to babysit. DunSocial is the hosted answer: one flat **$20/mo**, nothing to patch, back up, or restart. Start a [14-day free trial](https://app.dunsocial.com/login) when you're ready to connect accounts & run the test.

## The smart path: Postiz MCP → Markdown → DunSocial MCP

There's no silent black-box import here, & that's the point. You get a reviewable Markdown dump, a test run, & human confirmation before anything goes live:

1. **Connect Postiz's MCP server.** Get your API key from Postiz Settings → Developers → Public API, then add `https://api.postiz.com/mcp/YOUR_API_KEY` as a custom MCP connector in Claude, ChatGPT, or Cursor (self-hosting? swap that host for your own `NEXT_PUBLIC_BACKEND_URL`). Postiz documents the setup in its [MCP introduction](https://docs.postiz.com/mcp/introduction).
2. **Ask the assistant to dump the upcoming queue** into Markdown files. One post per file works well: channel, scheduled time, body, media notes, thread order if needed.
3. **Connect DunSocial MCP** at `https://api.dunsocial.com/api/mcp` in the same client. DunSocial's hosted MCP ships **53 tools** & is included in the plan, with no server of your own to run it on. See [DunSocial MCP](/mcp).
4. **Point the assistant at those Markdown files** & ask it to create drafts & schedules through DunSocial. Keep human confirm on before publish.
5. **Run a small test prompt yourself** (one or two posts), open the app, then check the calendar the next day before you deepen the cutover.

Want the side-by-side first? Skim [DunSocial vs Postiz](/compare/dunsocial-vs-postiz), the [Postiz alternative page](/alternatives/postiz), or [best Postiz alternatives with brand memory](/blog/best-postiz-alternatives-with-brand-memory), then come back here for the move.

## Why people are moving off self-hosted Postiz

The Postiz software is open source & free to download. Running it is a different story:

- **It isn't a one-container weekend project.** Postiz's own docs list Postgres & Redis as required services, plus (since v2.12.0) a full [Temporal workflow stack](https://docs.postiz.com/self-host/installation/system-requirements) that brings its own second Postgres & an Elasticsearch instance. A third-party review put the result at **"a 2GB to 4GB server and six to nine containers"** ([Postiz Review, creatortribune.com](https://creatortribune.com/postiz-review/)), & [Railway's Postiz-with-Temporal template](https://railway.com/deploy/postiz--postiz-with-temporal.md) lists eight services, including two separate Postgres databases.
- **You still register your own platform apps.** [Postiz's provider docs](https://docs.postiz.com/self-host/providers/overview) confirm most channels need you to register a developer app & supply the keys yourself. The same review put it plainly: **"you must get your own developer apps approved by TikTok and Meta, which can take weeks or stall entirely."**
- **More moving parts means more ways for a post to get stuck.** When your scheduler depends on a workflow engine, a database, & a cache all starting in the right order, a bad restart can leave posts waiting with no obvious error. That's your problem to debug, usually at the worst possible time.

DunSocial removes that whole job. It's hosted, you connect accounts with a normal sign-in instead of registering your own developer apps, & your posts go out without a container you have to watch. You get AI Memory & Voice Presets so every draft sounds like you, hosted MCP with 53 tools, & human confirm before publish, all for **$20/mo** flat.

## Fit check before you move

DunSocial publishes to **X, LinkedIn, Instagram, Threads, Bluesky, Reddit, Pinterest, YouTube Shorts, Discord, & Slack**, with TikTok & Facebook Pages in limited beta. If your Postiz queue lives on those networks, this guide covers the whole move.

**Price:** $20/mo or $192/yr, with a 14-day free trial, 1 seat in the base plan, & extra seats at $8/mo. Postiz Cloud's Standard plan is $29/mo for 5 channels, & self-hosting swaps the software fee for the server, database, & Temporal stack above. Confirm current numbers before you buy; see [pricing](/pricing).

**MCP:** 53 tools, included on the base plan & hosted for you. Endpoint: `https://api.dunsocial.com/api/mcp`.

## Setup (once)

Do these steps once. After that, the prompts below reuse the same connectors.

### Connect Postiz MCP

In your AI client, add a custom MCP connector pointed at `https://api.postiz.com/mcp/YOUR_API_KEY` (get the key from Postiz Settings → Developers → Public API), or use the Bearer-token variant at `/mcp` if your client supports it. Confirm the assistant can call `integrationList` & see your connected channels. If you're self-hosting, use your own instance's URL instead of `api.postiz.com`.

### Start DunSocial & connect accounts

[Log in or start the trial](https://app.dunsocial.com/login), then connect your networks in the DunSocial app first. MCP needs those accounts in place before it can create drafts against the right channels.

### Connect DunSocial MCP

In DunSocial, open Settings → MCP & add `https://api.dunsocial.com/api/mcp`. Approve the workspace scopes your assistant needs. Posts created through MCP are tagged with source "MCP" in the app, which makes the migration trail easy to audit. Details & tool coverage are on the [MCP page](/mcp). Prefer the CLI? The same workspace also works with the [DunSocial CLI](/cli).

### Save brand voice

Before you bulk-recreate, set AI Memory & a Voice Preset. The test prompt should prove voice & scheduling, not just that a draft appeared. It's what makes DunSocial drafts sound like you from the first post.

## Migration checklist

Work the list in order. The test step & the next-day check are what keep you from double-posts & gaps.

### 1. Dump the Postiz queue to Markdown

With Postiz MCP connected, paste the **dump Postiz queue to Markdown** prompt below. Ask for the next 14 days (or whatever window covers your live schedule). Aim for a folder like `./postiz-export/` with one Markdown file per post: channel, ISO scheduled time, body text, media URLs or "needs re-upload," & thread order if applicable. Don't delete or edit anything in Postiz during the dump.

### 2. Review the Markdown (human gate)

Skim every file. Keep, drop, or rewrite. This is the gate: you decide what's worth recreating before an assistant touches it, & it's a good moment to cut posts that no longer fit your voice. Note media that needs a fresh upload into DunSocial.

### 3. Test the prompt (before the full queue)

Paste the **test migrate one or two posts** prompt. It should create drafts for the first two posts only & tell you exactly what to open in the app. Don't publish yet. Open DunSocial, review those drafts, & confirm the schedule looks right before you scale.

### 4. Recreate the rest via DunSocial MCP

When the test looks good, paste the **migrate the rest after test passes** prompt. Prefer draft plus schedule over publish-now. Attach media through DunSocial's media flow when URLs alone aren't enough. Keep human confirmation on.

### 5. Pick a handover date & avoid doubles

Choose a cutover day. New work lands in DunSocial from that point. Cancel or pause the matching Postiz schedule so nothing fires twice.

### 6. Check the next day

The morning after: open the DunSocial calendar & confirm yesterday's posts went out once, previews matched, & nothing failed silently. Only then deepen the cutover.

### 7. Retire Postiz

After the next-day check passes, cancel your Postiz Cloud plan, or, if you were self-hosting, shut the stack down: stop & remove the containers, then decommission the server that ran Postgres, Redis, & Temporal. Export any analytics you still want first. From here, there's nothing left to maintain.

## Copy-paste prompts

Use these as written. Adjust the date window or folder name if you need to, but keep the "drafts first / no publish without confirmation" constraints.

### Dump Postiz queue to Markdown

<CodeSnippet
	label="prompt"
	highlight={false}
	code={`Using Postiz MCP, call integrationList to see my connected channels, then list every scheduled post for the next 14 days. For each post write a Markdown file in \`./postiz-export/\` with channel, scheduled time (ISO), body text, media URLs or "needs re-upload", and thread order if applicable. Do not delete or edit anything in Postiz.`}
/>

### Test migrate one or two posts

<CodeSnippet
	label="prompt"
	highlight={false}
	code={`Using DunSocial MCP and the files in \`./postiz-export/\`, take the first two posts only. Create drafts in my DunSocial workspace (do not publish now). Match channel and time as closely as supported. Tag or note source as migrated-from-Postiz. Then tell me exactly what to open in the DunSocial app to review.`}
/>

### Migrate the rest after test passes

<CodeSnippet
	label="prompt"
	highlight={false}
	code={`Using DunSocial MCP and every file in \`./postiz-export/\`, create drafts (prefer draft + schedule over publish-now). Match channel and time for platforms DunSocial covers (X, LinkedIn, Instagram, Threads, Bluesky, Reddit, Pinterest, YouTube Shorts, Discord, Slack, TikTok and Facebook Pages beta). Summarize what you created and what you skipped. Do not publish without my confirmation.`}
/>

## Common mistakes

- **Shutting down the Postiz server before the next-day check.** Prove DunSocial is firing correctly first, then decommission.
- **Skipping the test prompt** & dumping the whole queue blind.
- **Publishing from MCP** without human confirm. Keep confirm on until you trust the mapping.
- **Leaving the same post scheduled in both tools.** That's how you get doubles.

## After the switch

Once the calendar is yours again & the server is off, DunSocial is set up for how founders already work: Daily Ideas for the next posts, AI Memory & Voice Presets so drafts stay on-brand, & MCP so you can ship from Claude, ChatGPT, or Cursor without a Docker Compose file to maintain in the background. The same 53 MCP tools that helped you migrate stay available for everyday drafting & scheduling.

If you haven't started yet, open the [trial](https://app.dunsocial.com/login), connect your accounts, & run the three prompts above in order. Pricing & seat details are on [pricing](/pricing). Broader product questions live in the [FAQ](/faq).

## FAQ

### Is Postiz actually free?

The software license is. Running it isn't: Postiz's own docs require Postgres, Redis, &, since v2.12.0, a Temporal workflow stack with its own second Postgres & Elasticsearch, which one review sized at a 2GB-4GB server running six to nine containers. Postiz Cloud skips the server but starts at $29/mo for 5 channels. DunSocial is $20/mo, hosted, for every supported network.

### Do I need to copy-paste every post by hand?

No. The assistant does the heavy lift through MCP. You review the Markdown dump, run the test prompt, & confirm drafts in the DunSocial app.

### When do I shut down my Postiz server?

After the test prompt looks right & the next-day calendar check passes. Cancel or pause matching Postiz items on the handover date, confirm nothing double-posts, then decommission last.

### Is MCP included with DunSocial?

Yes. DunSocial MCP includes 53 tools & is part of the plan, fully hosted with no server of your own required. Endpoint: `https://api.dunsocial.com/api/mcp`. See [DunSocial MCP](/mcp).

### Can I review posts before they go live?

Yes. Human confirmation before publish is how DunSocial works. Prefer drafts (& scheduled drafts) during migration, then approve in the app.

## Sources

- Postiz: [MCP introduction](https://docs.postiz.com/mcp/introduction), [self-host system requirements](https://docs.postiz.com/self-host/installation/system-requirements), [provider setup](https://docs.postiz.com/self-host/providers/overview)
- [Postiz Review, creatortribune.com](https://creatortribune.com/postiz-review/)
- [Railway's Postiz-with-Temporal template](https://railway.com/deploy/postiz--postiz-with-temporal.md)

Retrieved 25 September 2026.

---

## About this document

This is the Markdown representation of https://www.dunsocial.com/blog/switch-from-postiz-to-dunsocial. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`.

Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt

## Company

- Product: DunSocial, https://www.dunsocial.com
- Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India
- Support: support@dunsocial.com
- Open the app: https://app.dunsocial.com/login