Why Your Data Is Fragmented
Business data is almost never in one place. Sales records come from your e-commerce platform. Marketing metrics come from ad networks. Customer profiles come from your CRM. Financial data comes from accounting software.
To answer cross-functional questions ("What's our customer acquisition cost by channel?" or "Which product category yields the highest margin?"), you need to combine these sources.
Traditionally, that means:
- Manual copy-paste across spreadsheets (slow and error-prone)
- SQL joins across database tables (requires a developer)
- Python/pandas scripts (requires programming skills)
- Paid ETL tools or dedicated data engineers (expensive)
ParseBase makes this accessible to anyone.
Merge: Join Files by Common Columns
Upload two or more files and specify which columns to match. For example:
- Join orders with customers on Customer ID
- Join transactions with products on Product SKU
- Join employees with performance data on Employee ID
This works like a SQL JOIN but requires no code. ParseBase handles column matching and presents the unified result as a single dataset you can query and chart.
Append: Stack Similar Files
When you have the same type of data split across periods (January sales, February sales, March sales), stacking combines them into one continuous dataset. ParseBase auto-maps matching columns and handles minor schema differences.
Transform: Reshape Your Data
The transformer tool lets you:
- Rename or remove columns
- Filter rows by conditions
- Aggregate data (sum, average, count by group)
- Create calculated fields
Real Example: E-Commerce Cross-File Analysis
A Shopify store owner has three exports:
- orders.csv: Order ID, Customer ID, Product SKU, Revenue, Date
- customers.csv: Customer ID, Name, Region, Signup Date
- products.csv: Product SKU, Category, Unit Cost, Supplier
In ParseBase:
- Upload all three files
- Merge orders with customers on Customer ID
- Merge the result with products on Product SKU
- Ask: "What's the profit margin by region and product category?"
Two minutes. No SQL. No Python. The store owner now has insights that would typically require a data analyst.
Merge vs. Append: When to Use Each
| Scenario | Use |
|---|---|
| Different data types sharing a common ID | Merge (Join) |
| Same data type from different time periods | Append (Stack) |
| Orders + Customers + Products | Merge |
| Jan Sales + Feb Sales + Mar Sales | Append |