Import your calendar from another scheduler
Upload a CSV from Metricool or Hootsuite, map the columns, and your next two weeks land on the calendar as drafts, even before every channel is reconnected.
Published Sep 2, 2026
1. Works with Metricool and Hootsuite's own exports; Buffer and Later are different
Metricool's and Hootsuite's native CSV exports map in directly. Buffer's export only covers posts already published, not the forward-scheduled queue, so it isn't a fit here. Later has no compliant automated export at all. Request one from Later's own support and reformat it into a CSV, or re-create your next two weeks directly in the composer.
2. Two required columns; the rest map automatically
Caption and scheduled date/time are the only mappings that have to be set. The upload step guesses both from your column headers, along with platform and media URL where present. Every guess is shown and editable before you confirm; nothing is mapped silently.
3. Both common export date formats are handled
ISO 8601 (with or without a timezone) and the US MM/DD/YYYY HH:mm format both parse correctly. A zone-less date is read as UTC explicitly, not assumed to be whatever timezone the import happens to run in. Left unhandled, that is a real source of scheduled times that are silently wrong.
4. A platform column doesn't have to match our names exactly
Common alternates resolve automatically. "Twitter" maps to X, "IG" to Instagram, and a few others. A value that still can't be resolved doesn't drop the row; you assign the platform manually for that row before confirming.
5. Everything imports as a draft, even before you reconnect a channel
Rows targeting a platform you haven't connected yet still land on the calendar as drafts. You see your next two weeks populated immediately, then connect what's missing. The screen after import names exactly which platforms still need a channel connected, one link per platform, not a generic reminder.
6. Up to 500 rows in one file
Enough for several months across a handful of channels. A file with more rows than that is rejected up front with the exact count, before anything is read row by row.
More guides
How to connect PostEase to Zapier or Make
Every publish can POST a signed payload to a Zapier Catch Hook or a Make custom webhook, carrying the caption, the account and a link to the live post. No app listing needed, and you can send a test event to map the fields.
Connecting PostEase to the rest of your stack
The outbound webhook, Zapier and Make, importing a calendar from another scheduler, and the browser extension are one integration surface, not four separate things to discover on your own.
Adding alt text to the images you schedule
One field in the composer, sent to X, LinkedIn, Pinterest, and Bluesky with the image. What it is for, what the 500-character cap comes from, and why video is left out.
How to set your workspace timezone
Every time you see or type in PostEase is in one zone chosen for the workspace, not your browser’s. Posts already scheduled keep their exact time when you change it.
Bring your calendar with you.
Every channel you have, included. Adding another does not change the price.