Where Does Beagle IM Store Data on Mac?
Where Beagle IM keeps accounts and history on Mac, and why file copies are the wrong migration path.
Last updated
Beagle IM is the Mac XMPP client from the same team behind Siskin on iOS. Its data lives in the macOS app sandbox under a Containers path tied to the bundle ID. That folder is per install and invisible to normal browsing.
Direct file copies across machines rarely work since the container ID changes. Server side message archives are the actual migration path. Treat the local store as a cache and the server history as the record. Avatars and OMEMO fingerprints refetch on login, so a fresh container looks complete within minutes.
Where Beagle IM stores this, by platform
~/Library/Containers/org.tigase.messenger.BeagleIM/Data/Library/Application Support
Sandboxed Mac container with app support data inside. Per install ID that changes on reinstall. Migrate through server archives and re login, not file copies.
Frequently asked questions
How do I move Beagle IM history to a new Mac?
Re login on the new Mac and let the server resend history through message archives. The local container is sandboxed per install and does not transplant. Export important files first through the chat share sheet.
What is the difference between Beagle IM and Siskin IM?
Beagle runs on Mac while Siskin runs on iPhone and iPad. Both speak XMPP through the same Tigase libraries but keep separate local stores. Accounts do not share files across the two apps.
Notice an outdated path? Let us know.