#Sales Cloud110 discussing

Yes, this is expected behavior. Salesforce Web-to-Lead creates a Lead record but doesn’t automatically convert it into an Opportunity just because a matching Account exists. You’d need a separate Flow or Apex automation to handle that process. 

For the matching issue, check your active duplicate and matching rules first. Use a tool or software that uses Fuzzy matching logic to help you find out duplicates and accurate lead to account matching.  

Tools like LeadAngel can also help match incoming leads to existing Salesforce Accounts, even when company names have minor variations, so you can handle lead-to-account matching more accurately before deciding how to route or process the lead. 

Hi @Renu Mudhalwadkar

,  

did you ever find out the reason for the described behavior?  

I noticed the same behavior. When we search for a user in "Owner" filter we only see "XXX 's Team" as result coming up, even though this user doesn't have a role below him/her in role hierarchy (and doesn't have a team) and I don't know why. 

I still shows the correct data, but it is irritating for the users/managers. 

Thanks, Sue

To import all existing emails from a PST file, you can use Microsoft Outlook’s built-in Import/Export wizard. Open Outlook, go to File → Open & Export → Import/Export, select Import from another program or file, and choose Outlook Data File (.pst). Browse to your PST file, select the option to handle duplicate items, and choose the mailbox or folder where you want to import the emails. Click Finish to begin the process. 

If you need to import multiple PST files or migrate emails without relying on Outlook, you can use the

The gap you're hitting is that most tools only do Salesforce-to-Salesforce syncing, or syncing of files but not on a schedule.

CloudHQ the backup tier (not the sync tier you found) supports scheduled backups of Salesforce records as CSV plus files to SharePoint; check their backup product specifically.

Skyvia does Salesforce -> SharePoint Files export with scheduling, field selection, and filters.

DIY: Salesforce Data Export Service does weekly CSV exports; script out their Data Loader CLI to push those to SharePoint.

One caveat is that these are all exports, and not point-in-time backups; if they need to restore a deleted record back into Salesforce, check the restore path first.

For the SharePoint side specifically, the Kernel SharePoint Backup handles backup of SharePoint sites, document libraries, lists, version history, and permissions to local or NAS storage, with delta passes to skip already-saved items. It won't pull from Salesforce, but if the end goal is a clean, restorable copy of that data sitting in SharePoint, it covers that half.