Import cPanel Email Forwarders from CSV or Excel Carefully

cPanel Address Importer can create several forwarders from a structured file. It does not copy existing mailbox messages, passwords, folders or a full hosting account. Importing forwarding rules is therefore not a complete email migration.

Prepare a small, controlled file

Use one source and destination per row, with source addresses belonging to the domain you manage. Do not put an unrelated Gmail account in the source column and expect cPanel to control its incoming mail. This illustrative CSV contains no passwords and sends no messages by itself:

Source,Target
sales@example.com,team@example.net
billing@example.com,accounts@example.net

Replace documentation domains only with authorized addresses. Confirm the chosen domain, destination ownership, duplicates, existing rules and loop risks before upload. Keep a private record of the current configuration and start with a small subset. A forwarder import does not need mailbox passwords; do not add secrets to the file just because the importer also supports account creation.

Import and map the columns

1. Open the verified HTTPS cPanel service and Email > Address Importer.
2. Select Forwarders, not Email Accounts. Choose the file. cPanel documents CSV and legacy Excel .xls support; do not assume every spreadsheet extension is accepted.
3. For CSV, select the delimiter actually used and mark the header-row option only if the first row contains labels.
4. Review the preview and explicitly map source and destination fields. Ignore unused columns and select the correct domain rather than relying on a guessed default.
5. Continue to the confirmation, inspect the intended rows and finish. Read any per-row errors instead of assuming every rule was created.

Verify the resulting rules and delivery

Open Forwarders and compare the saved source/destination pairs with the intended inventory. Send harmless authorized tests through the actual receiving service and check destination results, spam folders, delivery errors and any local mailbox copies. If MX records point elsewhere, importing local rules does not redirect that external provider.

Do not assume a failed or partial import rolls everything back automatically. Inventory what actually changed, then remove only incorrect new entries and restore the previous intended rules. Protect or remove the local import file according to your retention requirements; never publish an address inventory in the web root.

For InterServer-assisted web-hosting migrations, the confirmed scope is cPanel-to-cPanel or DirectAdmin-to-DirectAdmin only. This importer is not a promise of cross-panel, VPS or dedicated-server migration assistance.

References: cPanel Address Importer and forwarder behavior and verification.

Reviewed October 15, 2026. The illustrative CSV was checked for structure and example-address scope only; no panel import or customer delivery was executed.