Salesforce Leads Export Sample CSV (Dirty + Clean)
A production-realistic Salesforce lead export (6,200 rows) engineered to expose validation errors that crash Data Loader bulk imports. The Salesforce quirk: strict validation on fields like LeadSource means even a single invisible character triggers INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST errors. The 'dirty' version includes LeadSource values with zero-width spaces (U+200B) invisible in Excel, malformed 15-character Lead IDs missing the checksum suffix (causing upsert failures), and embedded commas in company names. Perfect for testing API integrations, Data Loader workflows, and Marketing Automation migrations. Process everything locally — your lead data never touches a server.
This Salesforce dataset contains realistic, fully anonymized records. We purposely engineered it to include common messy data patterns—such as unmapped columns, dirty formatting, and duplicate IDs—so you can safely test your processing pipelines without exposing real PII.
💡 Pro Tip: Data Loader batch failed with INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST? The cause is a zero-width space you can't see in Excel. Strip invisible Unicode characters locally with Format Cleaner in 3 seconds.
⚡ Next Step: Not sure if your Lead IDs are 15-char or 18-char? Validate the entire file with CSV Schema Validator to catch malformed IDs before corrupting your Salesforce instance.
Data Schema Definition
| Column Name | Data Type | Description |
|---|---|---|
| Id | string | 15-char or 18-char case-safe Salesforce ID |
| FirstName | string | Lead first name |
| LastName | string | Lead last name (required field) |
| Company | string | Often contains embedded commas (e.g., Apple, Inc.) requiring quoting |
| string | Standard email address | |
| LeadSource | string | Restricted picklist; fails if contains trailing/zero-width spaces |
| Industry | string | Standard Salesforce picklist field |
Recommended Tools
Related Workflows
How to Anonymize Customer Data Before Sharing with ChatGPT or Claude
Your raw customer CSV contains toxic PII. Pasting it into ChatGPT sends that data to OpenAI's servers—risking a Samsung-style corporate leak. This SOP local-masks names, emails, phones, and IPs using browser-based hashing. It preserves column types and statistical structures for LLM analysis, rendering the output completely untraceable to real users.
How to Clean Apollo Exported Leads Before Importing into Cold Email Software
Apollo exports include 'guessed' emails and hidden spam traps. Importing raw Apollo CSVs into Instantly guarantees an automatic campaign pause. This 4-step workflow filters out non-verified addresses, purges role-based targets (info@, admin@), flags catch-all domains, and formats the header row for zero-mapping imports into Smartlead or Lemlist.
How to Convert Stripe Payout Reports into QuickBooks Import Format
Stripe's balance detail export dumps charges, refunds, and fees into a flat CSV (gross, fee, net). None of this maps to QuickBooks Online's rigid 3-column schema (Date, Description, Amount). While Stripe admits IIF files only work for QBD, SaaS connectors like A2X charge $49/mo to bridge the gap. This workflow splits your transaction types into specific Chart of Accounts buckets (Revenue, Merchant Fees), converts ISO 8601 timestamps to MM/DD/YYYY, and generates a CSV that passes QuickBooks import validation with zero reconciliation errors.
Clean WooCommerce Exports for Financial System Import
WooCommerce's native CSV export is notoriously hostile to accounting workflows. Product descriptions in the post_content column arrive wrapped in raw HTML tags and shortcodes like [woocommerce_reviews]. Custom meta fields (e.g., _regular_price, _sku) frequently shift columns when plugins inject hidden postmeta, and the post_date column alternates between Y-m-d H:i:s and Unix timestamps depending on your WordPress version. This SOP strips HTML remnants via regex, realigns displaced meta columns, and standardizes all date fields to ISO 8601 so QuickBooks and Xero accept the import without throwing schema validation errors.
Sample Datasets
Amazon FBA Settlement Report Sample Data
A representative Amazon Seller Central settlement report (TSV format) with 150 transactions. It covers all critical row types: Orders, Refunds, FBA Fees, Adjustments, and Transfers. The 'dirty' version includes common beginner traps like Transfer rows (which cause double-counting) and TSV delimiter issues that break Excel. The 'clean' version shows a collapsed profit summary ready for QuickBooks import. Ideal for auditing FBA fees or testing automated profit calculation scripts without exposing your actual store revenue. All processing runs locally — your financial data never touches a server.
Apollo.io B2B Leads Export Sample CSV (Dirty + Clean)
A realistic Apollo.io lead list (300 contacts) engineered with the exact data quality issues that destroy cold email deliverability. The 'dirty' version includes: duplicate emails from overlapping searches, role-based addresses (info@, admin@) that trigger spam filters, catch-all domains falsely marked as 'verified', and mixed-case names resulting in 'Hi jOHN' personalization disasters. The 'clean' version shows the output after deduplication and name normalization. Ideal for testing cold email platform imports (Instantly, Smartlead) to protect domain reputation, or CRM deduplication workflows in HubSpot and Salesforce. All processing happens locally — your lead data stays private.
Zendesk Tickets Export Sample CSV (Dirty + Clean)
A production-realistic Zendesk support ticket export (5,000 rows) engineered to expose the exact edge cases that break naive CSV parsers and ETL pipelines. The critical Zendesk quirk: 'Description' and 'Comments' fields contain embedded CRLF (\r\n) line breaks from customer emails. Parsers that don't respect RFC 4180 quoting rules will split a single ticket into multiple invalid records. The 'dirty' version includes embedded newlines, null assignees, and UTF-8 characters without a BOM header. Perfect for testing ETL robustness (Fivetran, Python), RFC 4180 compliance, and helpdesk migrations (to Freshdesk/Intercom). Your support data is processed 100% locally — nothing uploaded.
HubSpot Contacts Export Sample CSV (Dirty + Clean)
A realistic HubSpot contact export (8,500 rows) covering the data quality issues that break CRM migrations and warehouse schemas. The HubSpot-specific quirk: multi-select custom properties and system fields (like Lead Status) are exported as semicolon-separated strings (e.g., 'New;Qualified;SQL'). Data engineers unfamiliar with this will split fields incorrectly, destroying the taxonomy. The 'dirty' version includes semicolon strings, emails with trailing whitespace (causing duplicate re-imports), and inconsistent company casing. Ideal for testing CRM migrations (to Salesforce), Reverse-ETL dry runs, and building Dim_Contacts schemas. All cleaning happens locally — your contact database stays private.