#Desktop Integration3 debatiendo

Followed the article from salesforce that states:

1. Create a CSV file with the following fields.
   1. Title - file name.
   2. Description - (optional) file or link description.
      1. NOTE If there are commas in the description, use double quotes around the text.
   3. VersionData - complete file path on your local drive (for uploading documents only.
      1. NOTE Files are converted to base64 encoding on upload. This action adds approximately 30% to the file size. ( this will cause batch load errors on files over 5MB)
   4. PathOnClient - complete file path on your local drive (for uploading documents only).
   5. ContentUrl - URL (for uploading links only).
   6. OwnerId - (optional) file owner, defaults to the user uploading the file.
   7. FirstPublishLocationId - library ID.
   8. RecordTypeId - record type ID.

If you want to import all existing emails from a PST file, the right method depends on where you want those emails to be imported. It is important for a large mailbox to keep the folder hierarchy, attachments and message properties rather than exporting individual emails. 

In case the destination requires a different email format, then you may try

for bulk PST conversion. It can process single PST or multiple PST files in a folder and export the mailbox data to MBOX, EML, EMLX, MSG, NSF, TGZ, HTML, MHTML, PDF and IMAP file formats. Conversion preserves folder and subfolder hierarchy, email properties and attachments. 

For a complete mailbox, batch processing is useful because all selected PST data can be handled together. The Date Range filter can also be left unused when the intention is to process the entire PST rather than a specific period. 

Before importing the complete mailbox, test a sample PST and verify the resulting folder structure and attachments.

.

• Click New Remote Site.
• Enter a descriptive term for the Remote Site Name.
• Enter the URL for the remote site.
• Optionally, enter a description of the site.
• Click Save.