Skip to content

Switching to Picifer

How to switch social media tools without losing the queue.

You already pay for something. This page is the honest version of moving: what comes across in a CSV, what you have to reconnect by hand, and the four things no tool can bring with it.

  • 14-day free trial
  • No card required
  • 19 networks

The Picifer calendar after a bulk import, with a fortnight of posts in draft across Instagram, Facebook, LinkedIn and Google Business Profile, waiting to be scheduled.

In shortCan I move my scheduled posts to a new social media tool?

Your queue moves as a CSV. Your history does not move at all. Picifer imports up to 500 posts at a time from a spreadsheet, with dates, networks, media links, first comments and labels, and re-validates every row against the real network limits. Analytics, published posts and old conversations stay where they were collected.

Rows per import
500
Import as
Drafts first
Channels to reconnect
All 19
History that moves
None

What transfers

A spreadsheet in, a fortnight of drafts out.

Download the template, or just upload your own export: the importer reads your headings, shows you the mapping it guessed and lets you change it. Nothing is created until you press the button.

The columns the Picifer bulk importer understands
ColumnWhat goes in it
date2026-12-01 09:30, or 01/12/2026 09:30, or ISO. A date on its own is scheduled for 09:00. All in your workspace time zone.
contentThe post text. Re-checked against every target network’s character limit before anything is created.
networksSpace separated, like instagram facebook linkedin. Rows that name nothing use the channels you pick on screen.
media urlA link to an image or video already hosted somewhere. Picifer fetches it and attaches it to the post.
first commentUsually your hashtags. Published with the post on the networks that support one.
labelsYour own tags for filtering the calendar later.
campaignGroups a launch or a season together.
  • Commas, semicolons and tabs all work, as do the files Excel, Numbers and Google Sheets produce.
  • A row that cannot be published comes back with its line number and the reason, rather than disappearing.
  • Import as drafts, read them, then schedule. Choosing scheduled straight away is how a wrong time zone becomes 40 posts at 3am.
  • Posts already in Picifer export the same way, so you are never locked in here either.

The order to do it in

Six steps, one afternoon.

The only one with a deadline is the fifth. Everything else can wait until you have read the drafts.

  1. 1

    Before you start

    Export two things from your current tool: your scheduled queue and your analytics. The queue is what you are moving. The analytics are the only copy of your own history you will ever have, because no tool can hand its stored numbers to another one.

  2. 2

    Connect your channels

    Connect each account in Picifer. Nine of the 19 networks connect by signing in to the network itself, and Bluesky uses an app password you generate there. This is the step with the most waiting in it, so do it first.

  3. 3

    Import the queue as drafts

    Put your exported queue through the bulk importer and choose drafts, not scheduled. Up to 500 rows at a time. Every row is re-validated against the real network limits and anything that would fail comes back by line number rather than being quietly dropped.

  4. 4

    Read the drafts, then schedule them

    Check the calendar week by week. Fix the rows the importer flagged, confirm the times landed in the right zone, then schedule the lot. This is also when you notice the posts you were only keeping because they were already in a queue.

  5. 5

    Empty the other queue

    Do this before your first Picifer post publishes, not after. Two tools connected to the same account will both publish, and your followers will see everything twice. Delete or pause the other queue, then disconnect the accounts from it.

  6. 6

    Move what is not a post

    Point your link in bio at your new page and keep the old links alive while they are still in circulation. Reconnect your Google Business Profile location. Write your UTM convention down somewhere, because this is the moment it quietly changes.

The one mistake everybody makes

Two tools connected to the same account will both publish. If your old queue still has posts in it when your first Picifer post goes out, your followers see the week twice. Empty that queue first, then disconnect the accounts from it, then let Picifer start.

Honestly

What does not come across.

This is the longest section on the page on purpose. Anybody promising a complete migration is promising something the networks do not allow.

Your analytics history

Nothing can move it. The networks only return a window of recent data through their APIs, and your current tool’s stored numbers belong to it. Picifer starts collecting the day you connect, so export a final CSV from the old tool and keep it.

Posts you already published

They stay on the networks, where they belong. Picifer does not back-fill your past posts, so your calendar starts at the first thing you schedule here rather than showing years of history.

Old comments and replies

The inbox fills with what each network’s API still returns, which is recent activity rather than an archive. Conversations you answered last year are not coming across, and neither are the internal notes attached to them.

Approval history

Who approved what, and the review notes from a year of posts, stay in the tool that recorded them. If you need that for compliance, keep the old account readable for as long as your policy says.

Shortened link click counts

If your current tool shortens links, those clicks are counted on its domain. Switch to your own tagged links and the counting starts again, which is a good reason to do it on the first of a month.

Ads, audiences and boosts

Picifer publishes and measures organic posts. It does not place ads, so saved audiences, boosted campaigns and ad budgets stay in each network’s own ads tools, where they already live.

Learned best times

Picifer starts from the hours each network is generally busiest and builds your own day-by-hour heatmap from your results. Expect three or four weeks before its suggestions are better than a published average.

Your media library

Assets inside another tool have to be downloaded and re-uploaded, or referenced by URL in the import. The media url column handles the second case, which covers most people with images on their own site.

Your channels

Every account signs in again.

Connections are not transferable between tools: each network issues them per application. This is the slow part of the afternoon, so start here.

InstagramInstagram Business or Creator account
FacebookFacebook Page
XX profile
LinkedInLinkedIn profile or Company Page
TikTokTikTok account
YouTubeYouTube channel
ThreadsThreads profile
PinterestPinterest account (pins go to a board)
BlueskyBluesky account (app password)App password
MastodonMastodon account on any server
Google Business ProfileGoogle Business Profile location
TelegramTelegram channel or group, through your own botApp password
DiscordDiscord server (posts go to one channel)App password
TumblrTumblr account (you pick the blog per post)
FarcasterFarcaster account (casts go to your feed or a channel)App password
WordPressWordPress site, self-hosted or WordPress.comApp password
GhostGhost site (Admin API key)App password
DEVDEV (dev.to) accountApp password
HashnodeHashnode publicationApp password

Every plan includes all 19 networks, so there is no decision to make about which ones you are allowed to reconnect. See pricing

For bigger moves

Or do it with the API.

If a CSV is the wrong shape, or you are syncing from a system of your own, there is a versioned API with keys per workspace.

  • Bearer keys per workspace, with read, write and publish scopes
  • Posts, connected accounts, analytics, link in bio links and media
  • Errors in one shape, with a code your script can branch on
  • Rate limited per key, so a bad loop cannot take out your workspace

You can also leave Picifer the same way: posts and analytics export as CSV, and the API reads everything it writes. A tool that makes leaving hard is telling you something about how it expects to keep you.

Keys, not passwords

Only a hash of each key is stored, and you can revoke one without touching the others.

Per minute limits

Rate limits are enforced per key, so one script cannot starve your team.

CSV both ways

Import up to 500 rows at a time, and export your posts and analytics whenever you want.

Ask first

Send us a sample export at hello@picifer.com and we will tell you what will not map.

FAQ

Switching questions.

If yours is not here, email hello@picifer.com before you cancel anything.

Can I import my scheduled posts into Picifer?
Yes. Export them as a CSV from your current tool and put them through the bulk importer: up to 500 rows at a time, with a downloadable template. The importer maps your column headings for you, you confirm the mapping, and every row is re-validated against the real network limits before anything is created.
Will my posts publish twice during the switch?
Only if you leave the other tool connected with posts still in its queue. Both tools publish independently, so empty or pause that queue before your first Picifer post goes out, then disconnect the accounts from it.
Does my analytics history transfer?
No, and no tool can honestly promise otherwise. The networks return only a recent window through their APIs, and stored history belongs to the tool that collected it. Export a final CSV from your current tool before you cancel, and treat it as your archive.
What if my current tool will not export a CSV?
Most will, usually from the calendar or posts list. If yours does not, you can rebuild the next two weeks by hand faster than you think, or use the public API to create posts from a script. The importer template shows exactly which columns matter.
Is there an API for a bigger migration?
Yes. Picifer has a versioned public API with bearer keys and read, write and publish scopes, covering posts, connected accounts, analytics, link in bio links and media. It is the right route if you are moving hundreds of posts or syncing from another system.
How long does switching take?
Most of an afternoon for a single brand: connecting the channels is the slow part, and the import itself takes minutes. Start a 14-day trial and run both tools in parallel for a week with only one queue active, and nothing is at risk.
Can you help with the migration?
Email hello@picifer.com with a sample of your export and we will tell you which columns to map and what will not come across, before you commit to anything.

Run both for a week. Keep the better one.

Start a 14-day trial, import your queue as drafts and read it on the calendar. Nothing publishes until you schedule it, and nothing is at risk while the old queue is empty.

  1. Connect your channels
  2. Teach it your voice
  3. Approve your week

14-day free trial · No card required · Cancel anytime

Start free, no card needed