# How to Switch from Sprout Social to DunSocial

> Switch from Sprout Social to DunSocial: export your publishing queue, recreate it with DunSocial MCP, test one prompt, then check the calendar before cutover.

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

---

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

Sprout Social prices per seat, & that math stops making sense the moment a small team or a solo founder just needs a queue of drafts to go out on schedule. Switching means moving your live publishing calendar over without dropping a post: pull your upcoming Sprout schedule into Markdown, recreate it in DunSocial through its hosted MCP, test one small prompt yourself, then check the calendar the next day before you cut over fully.

This guide is for solo founders, indie makers, & small content teams who opened a Sprout quote for **Smart Inbox**, listening, or enterprise reporting they don't actually use, & mostly just want a reliable publish calendar at a price that doesn't scale per seat. Start a [14-day free trial](https://app.dunsocial.com/login) when you're ready to connect accounts & run the test.

For side-by-side context first, skim [DunSocial vs Sprout Social](/compare/dunsocial-vs-sprout-social) or the [Sprout Social alternatives page](/alternatives/sprout-social); if you're still comparing tools rather than ready to move, the [best Sprout Social alternatives under $100](/blog/best-sprout-social-alternatives-under-100) roundup covers more options side by side. The Buffer & Hootsuite versions of this same move are at [switch from Buffer](/blog/switch-from-buffer-to-dunsocial) & [switch from Hootsuite](/blog/switch-from-hootsuite-to-dunsocial).

## Why this migration looks a little different

Buffer & Hootsuite both ship an official MCP server that works from Claude or Cursor, so their side of the export happens through the same chat you're already in. Sprout Social also has an official MCP server, at `https://mcp.sproutsocial.com/mcp`, but as of writing, Sprout's own support docs say it's built & supported for **ChatGPT only**, & scoped to **TikTok published-post analytics**, not general publishing-queue access, & not documented or supported for Claude, Cursor, or Gemini.

That means the export half of this move is manual instead of agent-to-agent: you pull your upcoming queue from the Sprout **Publishing → Calendar** view yourself. The recreate half is still all MCP, on the DunSocial side.

## Why teams move from Sprout Social to DunSocial

- **A flat price instead of a per-seat bill.** DunSocial is $20/mo for the workspace, not per person. Adding a teammate is an $8/mo seat, not another $79 to 399.
- **AI that already knows your brand.** AI Memory & Voice Presets are pulled into every draft on every platform, so posts sound like you without re-explaining your positioning each time.
- **Draft & schedule from your AI assistant.** Hosted MCP with **53 tools** is included, so Claude, ChatGPT, Cursor, Gemini, or Copilot can plan your week & hand you drafts to approve.
- **Human confirm before publish.** Nothing goes live until you say so.

## 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 Sprout queue lives on those networks, this guide covers the whole move.

**Price:** DunSocial is $20/mo or $192/yr, flat, with a 14-day free trial, 1 seat included, & extra seats at $8/mo ($77/yr). See [pricing](/pricing).

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

**Sprout Social pricing snapshot:** Essentials from $79/seat/mo (billed yearly; $99/mo month-to-month), Standard from $199, Professional from $299, Advanced from $399, per [Sprout Social pricing](https://sproutsocial.com/pricing/). One seat on Essentials already costs nearly four times DunSocial's flat $20, & two seats on Standard run past $390/mo. That gap is why small teams run a short overlap & then cut over. Verify current numbers before you compare.

## Setup (once)

Do these steps once. After that, the prompts below reuse the same DunSocial MCP connection.

### Open your Sprout Publishing Calendar

In Sprout, go to **Publishing → Calendar** & switch to a list or week view that shows the next two weeks (or your live scheduling window) of upcoming posts across your profiles.

### Start DunSocial & connect accounts

[Log in or start the trial](https://app.dunsocial.com/login), then connect the overlapping 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` to your AI client (Claude, ChatGPT, Cursor, Gemini, or Copilot). Approve workspace scopes. Posts created through MCP are tagged with source "MCP," which makes the migration trail easy to audit. Details & the full **53 tools** are on the [MCP page](/mcp). Prefer a terminal? The same workspace works with the [DunSocial CLI](/cli).

### Save brand voice before bulk-recreate

Set AI Memory & a Voice Preset before you recreate the queue. The test prompt should prove voice & scheduling, not just that a draft appeared.

## Migration checklist

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

### 1. Write your upcoming Sprout queue to Markdown

With the Sprout calendar open, write one Markdown file per post under `./sprout-export/`: profile or network, scheduled date/time, body text, & media notes (or "needs re-upload"). This is a manual pass, not an MCP dump; see "Why this migration looks a little different" above. Don't delete or edit anything in Sprout while you do this.

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

Skim every file. Keep, drop, or rewrite. Note media that needs a fresh upload into DunSocial. 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.

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

Paste **Prompt A**. It should create drafts for the first two posts only, match network & time as closely as DunSocial supports, & tell you what to open in the app. Do not publish yet. Review those drafts & confirm the schedule. If the test fails, fix voice, media, or channel mapping before you scale.

### 4. Recreate the rest via DunSocial MCP

When the test looks good, paste **Prompt B**. Prefer draft plus schedule over publish-now. Attach media through DunSocial when URLs alone aren't enough. Keep human confirmation on. Ask for a short summary of what it created & what it skipped.

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

Choose a cutover day. New work lands in DunSocial from that point. Cancel matching Sprout items that shouldn't fire. A short overlap is fine if you're deliberate about which calendar owns each post.

### 6. Check the next day

The morning after: open the DunSocial calendar (& Sprout if still live). Confirm yesterday's test or early cutover posts went out once, previews matched, & nothing failed silently. Only then deepen the cutover.

### 7. Cancel Sprout Social

After the next-day check passes & the DunSocial calendar matches your intent, cancel your Sprout seats. Export any reports you still want first. From here, one flat workspace price covers your whole team's calendar.

## Copy-paste prompts

Use these as written. Adjust the date window or folder name if needed, but keep "drafts first, no publish without confirmation." Verify tool names in your client before a full cutover.

### Prompt A: Test migrate one or two posts

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

### Prompt B: Migrate the rest after the test passes

<CodeSnippet
	label="prompt"
	highlight={false}
	code={`Using DunSocial MCP and every file in \`./sprout-export/\`, create drafts (prefer draft + schedule over publish-now). Match network 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

- **Skipping the test prompt** & recreating the whole queue blind in one pass.
- **Publishing from MCP** without human confirm. Keep confirm on until you trust the mapping.
- **Leaving the same post scheduled in both Sprout & DunSocial.** That's how you get doubles.
- **Cancelling Sprout seats before the next-day check.** Finish the proof, then cancel.

## After the switch

Once the calendar is yours again, DunSocial is set up for how founders already work: AI Memory & Voice Presets so drafts stay on-brand, & MCP so you can draft & schedule from Claude, ChatGPT, Cursor, Gemini, or Copilot. The same **53 MCP tools** that helped you migrate stay available for everyday drafting & scheduling, & the [CLI](/cli) covers the same workspace from the terminal.

If you haven't started yet, open the [trial](https://app.dunsocial.com/login), connect overlapping accounts, & run Prompt A & B in order. Pricing is on [pricing](/pricing). For comparison context: [DunSocial vs Sprout Social](/compare/dunsocial-vs-sprout-social), [Sprout Social alternatives](/alternatives/sprout-social), & [best Sprout Social alternatives under $100](/blog/best-sprout-social-alternatives-under-100).

## FAQ

### Can I import my Sprout queue automatically?

Not fully. Sprout's own MCP server is ChatGPT-only right now & scoped to TikTok analytics, not general publishing-queue access, so the export step is a manual pass through the Sprout calendar into Markdown. From there, recreating drafts in DunSocial is all MCP, with human review before anything goes live.

### When do I cancel my Sprout seats?

After the test prompt looks right & the next-day calendar check passes. Cancel matching Sprout items on the handover date so nothing double-posts, then cancel your Sprout seats.

### Is DunSocial MCP included?

Yes. DunSocial MCP includes **53 tools** & is part of the plan. Endpoint: `https://api.dunsocial.com/api/mcp`. See [DunSocial MCP](/mcp).

### Can I review before go-live?

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

## Sources

- Sprout Social pricing: [sproutsocial.com/pricing](https://sproutsocial.com/pricing/)
- Sprout Social's official MCP server, ChatGPT-only & TikTok-analytics-scoped: [Sprout Social support: ChatGPT Integration Overview & Setup](https://support.sproutsocial.com/hc/en-us/articles/41085761844365-ChatGPT-Integration-Overview-and-Setup)

Retrieved 23 September 2026.

---

## About this document

This is the Markdown representation of https://www.dunsocial.com/blog/switch-from-sprout-social-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