Skip to content

Team Operations

Move Channels Between Client Workspaces

Move publishing connections into the right client workspace with a reviewed selection, same-owner permissions and safe publishing checks.

Move existing publishing connections when a client needs a different workspace under the same account owner. For example, a restaurant’s Facebook Page and Instagram account may start in a shared agency workspace. Move them into the restaurant’s dedicated workspace so its team can prepare future content in the right place.

This is a publishing connection move, not a transfer to another account owner or a migration of historical content.

Before moving

  • Make sure both workspaces are under the same owning account. You need permission to manage both workspaces and connect channels.
  • Check that the destination workspace is active and has the required plan access and channel capacity. A move does not purchase additional capacity.
  • Finish or cancel unfinished publishing work for the selected connections. Resolve processing or uncertain delivery outcomes before moving. Never resend a post just to clear an uncertain result.
  • If a selected channel is allocated to Postly CRM, remove that allocation through the CRM access workflow before moving its publishing connection. The move does not transfer CRM conversations.
  • Resolve duplicate destination connections or invalid provider authorization first.

Move in the dashboard

  1. Open the source workspace and go to Channels.
  2. Select Move channels and choose the connected publishing destinations.
  3. Choose the destination workspace, then select Review move.
  4. Check the destination name, selected channels and any audience-group warning.
  5. Select Move channels to confirm. If only part of a selection finishes or the response is uncertain, use Retry move to check the pending moves. Do not disconnect and reconnect accounts to resolve uncertainty.
  6. Check both workspaces afterward. Confirm the destination’s channel list and reviewer access, and rebuild any needed audience groups before preparing new posts.

If the selection or connection changes after review, review the updated move again. If no destination appears, check ownership, workspace status and your permissions.

What moves and what stays

ItemResult
Selected publishing connectionsMove to the destination workspace after confirmation
Posts and historical analyticsStay in the source workspace
Source audience groupsMoved channels are removed from those groups
Pending publishingMust be finished or cancelled before the move
CRM allocation and conversationsNot transferred by this publishing operation
Plan capacityRemains shared across the owning account; destination limits still apply

Move through API access or an AI assistant

The REST flow uses POST /v1/workspaces/{workspaceId}/channel-moves/preview, followed by POST /v1/workspaces/{workspaceId}/channel-moves. The URL identifies the source workspace. Discover connected channels first; use each selected channel’s parent_id as platform_id, and its channel_id in channel_ids. Each request covers one connected account.

Send destination_workspace_id, platform_id, channel_ids and a unique request_id to preview. Show the exact channels, destination and consequences to the user. After approval, confirm the unchanged selection with the returned review_token, the same request_id and confirm: true. A completed move returns data.completed: true. Keep the same inputs when retrying an uncertain response so the service can recover the existing receipt.

MCP exposes postly.preview_channel_move and postly.move_channels. Supply workspace_id as the source, plus the same fields as REST. The API key needs write access to both workspaces owned by its account. MCP additionally requires workspace:manage and channels:connect consent and grants covering both workspaces and their organizations. A connection scoped only to the source is insufficient.

Refresh channel discovery in both workspaces after completion; parent IDs can change. Check the live assistant action catalog before using a public connector: deployment, renewed consent and marketplace review may affect availability. Do not claim a move succeeded if its tool is unavailable or the response is uncertain.

See the API reference, request examples and recovery guide.

Questions agencies ask

Can I move channels to a different customer’s owning account?

No. Both workspaces must have the same owner. Agree on a separate offboarding process if account ownership is changing.

Can I move only some pages from a connected provider account?

Select the publishing destinations you need in the dashboard. API/MCP requests group selected channel IDs by their connected account’s parent ID. Destination duplicates and provider-specific restrictions can block a selection; review the returned message before changing it.

Will scheduled posts follow the connection?

No. The supported move is connection-only. Finish or cancel unfinished publishing work before moving, and prepare new content in the destination afterward. Historical posts and analytics remain in the source.

Do I need to reconnect the social account?

Use Move channels for an eligible existing connection. If its authorization is invalid, restore the connection first. Do not disconnect accounts merely because a move response is uncertain; retry the same move to check its result.

Previous guide

Custom replies (first comment) across editors, CSV, Google Sheets, API and MCP

Shared comments, platform overrides, text, attachments and publication delays.

Next guide

Fix Bluesky video uploads: verify your email

Verify your Bluesky email and retry a failed video destination without duplicating posts on channels that already published.

Related guides