Transfer by Zapier, transfer existing data or a Zapier bulk import
Transfer pushes records you already have through a Zap, so historic data gets handled the same way as new data. Each record is its own Zap run, so plan the task count first.
A Zap normally only handles new events from the moment it's switched on. Transfer deals with everything that came before, like the last two years of clients you want in ClickUp.
The data goes into a Zapier Table first, imported from a CSV, Airtable, Excel, Google Sheets or Slack. Then from the Zap you choose Transfer data, pick the table and records, map the fields and confirm.
The Zap has to have been published at least once and be switched on. You can transfer up to 25,000 records at a time, and each record shows as its own run in Zap history. Each run's actions use tasks as normal, so a large back fill can use a lot of your allowance.
I use Transfer when a client moves to a new tool and wants their history to come with them, through the same Zap that'll handle new records. That way old and new data end up in exactly the same shape.
I always test with a handful of records first, and I check the task count against the client's plan before sending the rest. Because Transfer only works on a Zap that's switched on, I plan any back fill for after the Zap is published.
Every record is its own run. Count the actions in the Zap and the records you're sending, and check the test runs, before you start.
Up to 25,000 records at a time. Some apps have their own rate limits, so big transfers can take a while.
Yes. Each record runs through the Zap as its own run, and its actions use tasks as normal. Test with a few records to see the real count.
The Zap has to have been published at least once and be switched on. You can't transfer into a draft or a Zap that's off.
I set these up and train your team, in your own ClickUp or Zapier account.
Book a callContact Jack - jack@withtoki.co.uk