Move your tweets to Bluesky.
Bring your stories with BlueArk.
The service was designed for everyone! To use it, just make your X/Twitter account public, enter your @ there, also enter your Bluesky data and the rest is up to us!
Our system will quickly collect your public data from X/Twitter. Then, over time, we will gradually roll your data into Bluesky (more information below under "Export Time").
We haven't found a reliable way to find your X/Twitter followers on Bluesky yet. That's why we don't import the people you follow yet.
Since we can't match an X/Twitter account on Bluesky, we also don't import your RTs and quotes, because the tweet you retweeted or quoted probably doesn't even exist on Bluesky. So, at the moment, we only import the content of your tweets.
Of course, we also don't import your likes, saves, or the number of likes on your tweets.
Videos longer than 60 seconds are not yet allowed on Bluesky, so for an additional fee, we can host your longer videos and add a link to your post! Contact us to learn more.
Accounts that contain NSFW content may not be fully imported. Your first 3,000 tweets (approximately) will be imported, but after 3,000 tweets, our system uses X/Twitter search, which does not return results with sensitive content. Therefore, accounts with this type of contents are not guaranteed to be fully imported.
1. If the tweet has one or more videos +60s or videos larger than 50MB, the entire tweet will no longer be imported. To learn more about and request hosting for videos +60s or +50MB videos, the customer must contact us.
2. If the tweet has more than one video, the videos will be split into replies in the same thread (in no specific order).
3. If the tweet has one or more videos and one or more photos, the photos will be published in the main post and the other videos as replies in the same thread.
4. If the tweet has +300 characters (Bluesky limit), it will be split into replies in the same thread, following the order of the text, which will be interrupted at character 297 to add the ellipsis (...), completing 300 characters.
NOTE: For Bluesky, videos with exactly 60 seconds are considered as +60s, therefore, rule 1 will be followed.
Bluesky allows posts to be made with an old date, that is, today we make a post with a date from 2015, for example. That's why we can import your history.
Our system uses the X/Twitter integration APIs to access your tweets on the platform. This API only accesses public tweets, so your account cannot be a closed account. We make several calls to these APIs to obtain all of your account data. In other words, we create a copy of your account's public data in our database. Your tweets, replies, media, etc. All of your public content is downloaded to our servers.
However, it is important to note that, due to limitations of X/Twitter itself, it is not possible to guarantee the collection of 100% of your tweets. To collect your tweets, we use X/Twitter's search. The social network's search does not always return all the results that actually exist in the account, especially those categorized as sensitive or involving specific restrictions and retweets. By contracting the service, you agree and understand that some of your tweets may not be collected, due to these limitations. To ensure greater completeness, you can complement your migration with your tweet archive for free, if you wish.
Most of the content that is not collected, as mentioned in the previous paragraph, is NSFW content and retweets. Retweets will not be exported, in any case, so their collection is irrelevant but impacts the final number of tweets collected/processed and tweets in the account.
After collecting your data from X/Twitter, our system processes all of these tweets to determine what can be imported into Bluesky and what cannot, and in what order everything should be published. As mentioned before, not all content can be imported, especially content that involves other people's tweets.
Once we have determined the tweets to import, we delete all other tweets that will not be imported from our database. In order to avoid retaining unnecessary information about your account.
Finally, our system processes the tweets to import in queues, from the most recent tweet to the oldest. Connecting to your Bluesky account and publishing the tweet via Bluesky's open protocol - AT Protocol.
Bluesky has an absolute limit of 35,000 operations per day per account. Let's say that these operations are points. Browsing the timeline, using the app or on a PC, consumes some of these points. Each post published consumes an average of 3 points.
To avoid impacting your use of Bluesky, we limit our export to 9,600 posts per day. In other words, these 9,600 posts consume 28,800 points, leaving another 6,200 points free, without interfering with your regular use of Bluesky. Therefore, the maximum daily export limit is 9,600 posts.
Posts are published every 5 minutes, that is, over the course of 24 hours, there will be 288 publication windows (24 hours ÷ 5 minutes). 33 posts will be published every 5 minutes. For accounts with less than 9,600 posts to export, the frequency is higher, reaching up to 50 posts every 15 minutes.
Starting at the import start, the service is non-refundable. Before that, while we are still approving the start of your migration, you can request a partial refund, which will deduct 6% + U$0.35 due to Stripe's payment and operation fees. Once the export is initiated, there is no possibility of cancellation and refund of the amount paid, due to the costs and processes involved.
By clicking on "Create Import" and continuing to purchase the service, I declare that I am aware of the terms and conditions for carrying out the import and I agree that BlueArk has access to my Bluesky account only to import my content.
If you have any questions, we'd be happy to hear from you! Just send an email to [email protected].
To check the progress of your operation, enter the code that was generated when you created it below. The operation code was also sent to the email address provided.
Check ProgressI don't have a code yetI lost my code--
Send your X/Twitter exported data archive to get a best export result.
The file must be in a pristine, unmodified format, as it was downloaded from X/Twitter. Compressed file in the ZIP format (.zip).
We're still importing your tweets to our database, therefore, the numbers below are still being determined. The number at "posts to export" and the "posts generated for each year" table below will only be updated after the import ends.
Check out the classification of your collected tweets below. Find more explanations about this number in the disclaimers at the end of the tables, or on the service details page.
The difference between tweets on the account and tweets collected occurs because we collect your tweets through X/Twitter's own search. X/Twitter's search does not return your retweets and sensitive content, indicating that this difference can be explained by these contents. Retweets are not imported anyways, and do not impact the final result. Accounts with sensitive content, just like any other account, may use the "boost your migration" feature to fill the gaps.
The number of posts generated may be greater than the number of potentially exportable tweets, since a single tweet with 2 videos, for example, will be divided into 2 posts. Or tweets with long texts (+300 chars), in the case of subscribers to X/Twitter's paid plans, the text will also be divided, resulting in more posts, for example. Learn more on the service details page.
The number of posts generated may be less than the number of potentially exportable tweets because this number does not consider tweets that were made in someone else's thread. The number "potentially exportable tweets" checks whether the tweets related to it (quote, parent and retweet) are from the same account. The number of generated posts is based on a reconstruction of the threads to determine whether a tweet has an external relationship or not.