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.
This Hubspot 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: HubSpot just created 890 duplicate contacts because of trailing spaces in your import file. Hit this CSV with CSV Deduplicator to fuzzy-match on email, trim whitespace, and merge the richest row.
⚡ Next Step: Semicolons in Lead Status breaking your ETL? Run it through Format Cleaner to normalize multi-select fields and make it warehouse-ready.
Data Schema Definition
| Column Name | Data Type | Description |
|---|---|---|
| Contact ID | integer | HubSpot unique internal ID |
| First Name | string | Contact's given name |
| Last Name | string | Contact's family name |
| string | Often contains trailing spaces causing duplicates | |
| Lead Status | string | Semicolon-delimited string (e.g., New;Qualified) |
| Lifecycle Stage | string | Often blank if bypassing form submission |
| Associated Company | string | Inconsistent casing breaks ABM segmentation |
Recommended Tools
Related Workflows
How to Merge 50 Shopify Order CSVs Into One File Without Crashing Excel
Shopify caps order exports at ~10,000 rows. Paste a few months of high-volume store data into Excel, cross 150K rows, and watch it freeze ('Not Responding'). This workflow merges dozens of fragmented CSVs, deduplicates by Order ID, and realigns shifted columns (like missing Billing Country in older exports). The output is a clean, flat table ready for Triple Whale ingestion, Pivot Tables, or LTV/ROAS analysis.
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.
Sample Datasets
Shopify Order Export Sample CSV (Dirty + Clean)
A production-realistic Shopify order export (200 rows) covering the exact scenarios that break data pipelines: multi-line items (one order → multiple rows), partial refunds, mixed fulfillment statuses, and discount code stacking. Download both a 'dirty' raw export (containing trailing spaces and HTML entities) and a 'clean' normalized version. Perfect for testing ShipStation ERP imports, QuickBooks reconciliation, or Shopify API mock data. All data processing happens locally in your browser — your order data never leaves your machine.
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.