How Do You Mass-Forward or Import Past Telegram Messages?

First, the warning

Bulk forwarding is the riskiest thing you can ask a Telegram account to do. Every delivery is a request, hundreds of requests in a row look like automation, and Telegram answers first with rate limits and then with restrictions on the account itself. The account being restricted is yours, not ours.

We publish our own numbers because they are the argument. Across every import ever run on Phantom Forwarder we measured 55,982 delivery attempts, of which 61 per cent failed, with 94 per cent of the whole volume produced by just seven oversized jobs. That measurement is where the caps below come from: they exist to protect your account, and they are the same on every paid plan, because a bigger number is a bigger risk rather than a better feature.

The three import modes

• Everything: the full history of the source chat, up to the cap.
• Date range: only what was published between two dates, which is the mode to use when you are moving a specific period.
• Last N messages: the most recent ones only, and the safest way to test the setup before committing to a bigger job.

The caps, and what exactly they count

• 500 deliveries per source channel, once and for all. A channel that has been drained stays drained.
• 1,500 deliveries a day across all your channels, as a brake against splitting one big job into many small ones.
• The count is deliveries, not messages: one message sent to three destinations is three deliveries, because that is three requests to Telegram.
• On the 7-day trial: one import of 50 messages, once.
• On the Free plan: importing past messages is not included.
• The cap is identical on Smart, Gold and Platinum. It can be raised by hand for a paying customer who asks and explains, but it is never something you buy.

How to run an import

One import runs at a time per account. That is on purpose: two jobs in parallel double the request rate coming from the same Telegram account.

1. Open Rules in your dashboard and use the menu on the rule you want to import into.
2. Choose Import History, then the mode: everything, a date range, or the last N messages.
3. Decide whether the rule filters and transformations should apply, so you can bring across only what matches instead of the whole history.
4. Leave the delay between messages at its default unless you have a reason to change it. It is what keeps the job below Telegram thresholds.
5. Start. Progress, delivered and filtered counts and the log update live, and you can stop the job at any point.

How to keep an import safe

• Import into a destination you own, so that a mistake is easy to undo.
• Test with the last 20 or 50 messages before running a bigger job.
• Use a date range instead of everything whenever you can name the period you need.
• Import once, and prefer quiet hours.
• If you genuinely need thousands of messages, ask support rather than splitting the job across many channels or days. Splitting is exactly what the daily cap is there to stop, and asking is both faster and safer.

What an import does not do

• It does not reach anything your own account cannot already read. Membership rules still apply.
• It does not recreate reactions, view counts or comment threads: those belong to the original chat.
• It does not recover messages that were already deleted at the source.
• It is not a backup product. It copies messages into another chat; it does not archive them for you.