Map brands to projects and destinations
Create an inventory with one line for each brand and social account. Next to it, record the Reeling project that would own that destination. A brand allowance and a project allowance are not interchangeable; the number of accounts within each workspace also matters.
For example, two brands each using YouTube and LinkedIn mean two projects and four connected channels in your planned Reeling setup. Check the live plan limits and account eligibility for those exact destinations. This is an illustrative inventory, not an imported customer account.
Decide what happens to client reports
If clients rely on your current reports, list their required fields, history range and delivery format before moving publishing. Export or retain records using the permissions available in your current account. Reeling’s metrics coverage differs by network; a successful publish does not establish equivalent reporting.
Choose a pilot where you can compare the actual published post and the metrics Reeling returns. Keep report delivery in the current tool if the required fields are absent. Do the same review for any external automation: an API or MCP connection does not imply that its tools, data or limits match.
Reconnect one real project
Create a Reeling account, open Projects and create the workspace for your pilot. Connect only the destinations in that pilot through their normal authorization flow. A connection in another scheduler does not transfer its credentials to Reeling. Confirm that the selected account, page or channel is the one you intend to publish to.
Check the current platform requirements before paying for a larger rollout. Instagram currently requires tester access in Reeling. TikTok inbox delivery still requires you to finish the post in TikTok; it is not public Direct Post. The developer matrix describes publishing, metrics and inbox coverage separately.
Recreate one representative post
Use media you own and a post whose destination requirements you understand. Copy the approved wording from your own source material, attach the final export, select the intended channel and check the schedule time and timezone. This guide describes a manual pilot: it does not promise an automatic import of queues, approvals, analytics history or social-account credentials.
Keep the pilot entry in the old queue paused or removed before scheduling the same content in Reeling. Keep the rest of the old queue in place until you have agreed on a cutover time. A shared worksheet helps avoid a post being sent by both tools.
Verify delivery before moving the queue
At the agreed time, inspect the result for each destination and open the resulting post on the social platform. A queued or accepted request is not proof of a public post. For a TikTok inbox workflow, complete the post in TikTok and verify it there. Record the destination URL and the result in the worksheet.
If delivery is unclear, inspect the existing post status before trying again. With the API, keep the returned post ID and read GET /api/v1/posts/:id. Do not repeat a publish request just because a response timed out: the first request may already have been accepted. If one destination succeeded and another failed, investigate that destination separately.
Choose a cutover date and keep a fallback
Move a small batch only after the pilot meets your acceptance criteria. Record the last post owned by the previous scheduler and the first post owned by Reeling. Recheck the timezone, account permissions and any manual completion steps. Keep an export or other permitted copy of the old schedule and reporting records before ending that subscription.
If a required approval, inbox or reporting step fails the pilot, keep that workflow in the existing tool while you resolve it. This is a setup checklist based on the documented Reeling workflow, not a claim that we migrated a customer account or reproduced every competitor feature.