Migrate directory structure from eM Client to Office 365

How do you migrate the directory structure from eM Client to Office 365? I can export the directory to my laptop but can’t import it into Office 365 and as far as I can see I need to purchase some software to convert files to .pst files. Is that right or am I missing something simple?
Thanks for any help you can offer.

Only can you take from eM Client as eml.
Here it is you convert to pst.
Get at this link:
HOW IT IS TO CONVERT TO PST

Torsten

doming0 23 julio 2023 :: 1245hrs (UTC +0100)

Here are 2 methods that we have used, they both work.

Two conversion methods that work

¡Suerte!

skybat

¡Los mejores desde Budapest la soleada y mantente a salvo!

[email protected]

Hablo español, luego portugués, inglés, francés y alemán
con conocimiento de varios otros idiomas.

There is actually nothing you need to export nor purchase.

The folder structure and its contents you see in your account in eM Client is synced from your server, where it is stored. All you need to do is add the same account to any other application, and you will see the same structure and messages.

If you have moved some data to Local Folders, move it back to the account, and it will sync back to the server, and any other application connected to that account.

Malwarebytes Browser Guard says that link contains a Trojan virus.

lunes 24 julio 2023 :: 0848hrs (UTC +0100)

Strange, I run Malwarebytes Premium fully updated with a Lifetime License and do not have a warning.
I as well run Surfshark that did not block the site.
A Google search and link does not block the site
I have reported your issue and the above to Malwarebytes (www.arysontechnologies.com)
I am aware that they are sometimes over zealous

¡Suerte!

skybat

¡Los mejores desde Budapest la soleada y mantente a salvo!

[email protected]

Hablo español, luego portugués, inglés, francés y alemán
con conocimiento de varios otros idiomas.

I also use Malwarebytes Premium lifetime - but that doesn’t pick it up, it was Malwarebytes Browser Guard extension in Microsoft Edge that caught it. Here are the details: