> ## Documentation Index > Fetch the complete documentation index at: https://docs.lusha.com/llms.txt > Use this file to discover all available pages before exploring further. # Not in my CRM filter > How to use the Not in my CRM filter in Lusha Search to exclude contacts and companies that already exist in your Salesforce or HubSpot account. The Not in My CRM filter hides any contact or company that already exists in your connected CRM from your Lusha Search results. This helps you avoid duplicates and spend your credits only on fresh leads. Supported CRMs: This filter is currently supported for **Salesforce** and **HubSpot**. ## How to use Go to **Home** and start a conversation in the chat, or click **Contact filters** or **Company filters** to go directly to the filter panel. Contact filters and Company filters options on the Home screen Apply your filters to define your search. In the filter panel, toggle on **Not in My CRM**. Your results will update instantly to show only contacts/companies not in your CRM. ## Filter states ## Not selected (default) When the filter is off, all matching contacts are shown - including those already in your CRM. Not in My CRM filter toggle in the off (not selected) state ## Contacts - Not in my CRM Hides contacts that already exist in your connected CRM. The objects checked depend on your CRM: * **Salesforce:** Contact, Lead, or Opportunity * **HubSpot:** Contact Not in My CRM filter applied to Contacts results ## Companies - Not in my CRM Hides companies that already exist in your connected CRM. The objects checked depend on your CRM: * **Salesforce:** Account or Opportunity * **HubSpot:** Company Not in My CRM filter applied to Companies results ## Use cases ## Switching between Contacts and Companies The filter is applied per tab. When you switch between Contacts and Companies, each tab retains its own filter state. Not in My CRM filter state retained separately for the Contacts and Companies tabs ## No filter selected When no CRM filter is active, all results are shown regardless of CRM status. Search results with no CRM filter selected ## No CRM connection If the filter appears to be failing entirely, follow these steps: Navigate to **Integrations** and ensure your CRM (Salesforce, HubSpot, Pipedrive, or Bullhorn) is successfully connected. Check that your **Integration Settings** allow Lusha to read your CRM records. Refresh your browser and re-apply the **Not in my CRM** filter from the **Lusha Search** filters menu. If you have recently changed field mapping in your CRM, you may need to disconnect and reconnect the integration to refresh the data sync. If the issue persists, contact Lusha Support for further assistance. Integrations page showing CRM connection status ## How many results the filter checks The filter runs across your entire search, no matter how large it is. If a search returns 800,000 results, all 800,000 are checked against your CRM - there's no result-count ceiling. This used to be capped at the first 10,000 results. That cap is gone, so the result count you see with the filter on reflects a check of the full result set. ## How quickly the filter picks up new CRM records The filter stays in step with your own work inside a single session. Export contacts to your CRM, run another search, and the records you just exported are already excluded. The round trip takes about 2 minutes. This means you don't need to scrub your table in the CRM after exporting - the table that leaves Lusha is already clean, and your credits go to net-new records only. ## Why am I seeing contacts already in my CRM? Understand why some contacts might still appear in your search results even when the "Not in my CRM" filter is active. ### How Lusha identifies duplicates Lusha uses specific data points to match records between our platform and your CRM: * **Email address:** The primary unique identifier. * **Name + Company:** A combination match used when an email isn't present. ### Why duplicates may still appear If you see a contact in Lusha that you know is already in your CRM, it is usually due to a data mismatch. Common reasons include: * **Job changes:** The contact has moved to a new company and has a different professional email address than the one stored in your CRM. * **Name formatting:** Variations in how names are recorded (e.g., "John Smith" in Lusha vs. "J. Smith" or "Jonathan Smith" in your CRM). * **Company name discrepancies:** Differences in legal names vs. trade names (e.g., "Lusha" vs. "Lusha Systems Inc."). * **Sync latency:** If a record was added to your CRM in the last couple of minutes, it may not be reflected in the filter yet. Records you export from Lusha are typically picked up within about 2 minutes. The reasons above are data-matching edge cases, not a coverage limit. The filter checks every record your search returns. *** You're all set! Toggle on **Not in my CRM** and your search results will show net-new records only.