Convert TXT to PST

A plain-text export must be placed in an Outlook data file when an archive, mailbox migration, or desktop Outlook workflow requires a .pst file. Because TXT contains no standard mail structure, the conversion must define which text becomes each Outlook message and which metadata is unavailable.

What the TXT format is

.txt is a plain-text format containing characters without native fields for senders, recipients, dates, folders, attachments, or HTML formatting. Notepad, TextEdit, command-line tools, scripts, and older applications commonly create TXT files. A text export may contain readable email headers and body content, but Outlook cannot treat those lines as message fields without an import rule.

What the PST format is

.pst is Microsoft Outlook's Personal Storage Table database format. It can contain mail, folders, contacts, calendars, tasks, and message metadata. Classic Outlook for Windows opens a PST through File → Open & Export → Open Outlook Data File.

A PST supports Outlook search, folder organization, local archiving, and access to mail without the original mailbox connection. It is a mailbox container, not a text document, so arbitrary prose cannot be converted into reliable sender, recipient, date, attachment, or message-ID fields.

How to convert one TXT file

For a single document, classic Outlook for Windows provides the simplest local method:

1. Create a new data file through File → Account Settings → Account Settings → Data Files → Add and save it as converted.pst.
2. Open the TXT file in a text editor, copy its contents, and create a new Outlook email.
3. Set the subject and any available recipients or date information manually, then paste the text into the message body.
4. Use File → Move to Folder or drag the saved message into the new PST. Saving the message in the default mailbox alone does not create a TXT-to-PST copy.
5. Verify the result by opening converted.pst with File → Open & Export → Open Outlook Data File.

This method creates one Outlook item from one text document. It does not reconstruct metadata that the TXT file does not contain.

How to batch-create messages

For multiple records, prepare a UTF-8 CSV with one row per intended message and columns such as Subject, To, and Body. Quote fields containing commas, quotation marks, or line breaks. The following Windows PowerShell 5.1 script uses the classic Outlook COM interface, creates a Unicode PST, and places messages in an Imported TXT folder:

$source = Join-Path $PSScriptRoot "message.txt"
$pst = Join-Path $PSScriptRoot "converted.pst"
$outlook = New-Object -ComObject Outlook.Application
$ns = $outlook.GetNamespace("MAPI")
$ns.AddStoreEx($pst, 2)
$store = @($ns.Stores | Where-Object { $_.FilePath -eq $pst })[-1]
$root = $store.GetRootFolder()
$folder = $root.Folders.Add("Imported TXT", 0)
$mail = $outlook.CreateItem(0)
$mail.Subject = "Imported TXT document"
$mail.Body = [System.IO.File]::ReadAllText($source, [System.Text.Encoding]::UTF8)
$mail.Save()
$mail.Move($folder) | Out-Null
$ns.RemoveStore($root)
$outlook.Quit()

Save it as txt-to-pst.ps1, change the filenames and subject, close unnecessary Outlook windows, and run it with powershell.exe -ExecutionPolicy Bypass -File .\txt-to-pst.ps1. The script assumes the source is UTF-8; select the correct encoding when the file is ANSI or uses another character set. For CSV input, replace the single-message block with a loop that assigns Subject, To, and Body from each Import-Csv row.

Tools and online services

Classic Microsoft Outlook is the appropriate desktop tool when the destination must be a genuine PST. Aid4Mail and ReliefJet Essentials are useful for structured email migrations and format conversions, but they cannot infer dependable mail fields from unstructured prose; confirm that the specific source format is supported before purchasing or processing a batch.

There is no dependable generic online TXT-to-PST conversion path. Services such as Zamzar or CloudConvert may convert plain text to document formats, but they do not turn arbitrary TXT into correctly structured Outlook messages. A service that accepts TXT and claims to produce PST must still define its handling of headers, folders, dates, and attachments. Do not upload private mail, credentials, personal data, or regulated records to an online converter.

Quality and compatibility limits

• Decide whether each TXT file represents one message or whether delimiters and headers divide it into several records before importing.
• Plain text cannot recreate HTML formatting, inline images, attachments, signatures, read state, conversation IDs, or original message identifiers. Attachments must be supplied separately and added with additional Outlook code.
• Incorrect character encoding can corrupt accented characters and non-Latin scripts. Convert the source to UTF-8 or specify its actual encoding during reading.
• Automation through Outlook COM requires classic Outlook for Windows; it does not work from Outlook on the web and is not provided by the new Outlook interface. PST features in newer Outlook builds vary, but classic Outlook remains the reliable automation target.
• Keep the PST closed while copying it. Reopen it through Outlook after conversion and inspect subjects, body text, folders, recipients, and character rendering.