Best practices

Tips we've learned from setting up thousands of bases

📦 Start with templates

The first time you use Whalesync, we recommend you duplicate one of our Template Packs. It's helpful to learn how syncing works in a controlled environment before connecting Whalesync to your production data.

📧 Use a team account to sign-in

If you plan on using Whalesync with your team, we recommend creating an account you don't mind sharing. For example, you may want to create an email such as "". In the future we'll build multi-account features that make this easier.

0️⃣ Start with one app empty of data

It's often best to start with one empty database for your first sync. While Whalesync can always sync data bidirectionally, starting with one of your two apps empty keeps your initial sync clean.

💾 Save backups of your data periodically

The Whalesync sync engine is incredibly fast and reliable. That being said, whenever you're moving data around, it's always good practice to save backups of that data. Apps like Airtable and Webflow make it really easy to take snapshots. We recommend doing this periodically.

⚠️ Be aware of the limitations of the apps you're connecting

Every app we integrate with has its own limitations. For example, Webflow requires the Name field is mapped in every collection. We do our best to share any app limitations directly in the product or in our docs.

🗣️ If you are stuck, check resources and then reach out

If you ever run into a problem you can't figure out, we have a range of resources to help. First, you can check our Common Errors docs. If your issue isn't covered there, join our Slack community and shoot us a note in the #i-have-an-issue channel. We'll do everything we can to help you get unstuck!

Last updated