See what needs fixing before an ERP import
These six fictional customer records run through Stratoryn’s analysis engine. No account or payment is needed. This sample contains a duplicate customer identifier and missing contact and tax information.
6 records checked · 3 records with issues
Data quality score: 87/100. Counts below are issue occurrences; a record can have several issues.
Duplicate CustomerId values
CRITICAL · 1 affected records. CustomerId must be unique; duplicate keys break record matching and can clash during matching or import.
Next action: Enforce uniqueness on CustomerId before migration.
| Source row | Record | Field | Value |
|---|---|---|---|
| 4 | 00124 | CustomerId | 00124 |
Missing tax/VAT ID
HIGH · 1 affected records. Missing TaxId may affect tax handling. Check the customer type, jurisdiction and destination requirements.
Next action: Review TaxId; populate it where your invoicing process or destination requires a tax identifier.
| Source row | Record | Field | Value |
|---|---|---|---|
| 6 | 00126 | TaxId | (empty) |
Missing values in Email
HIGH · 1 affected records. Email may affect finance, compliance or contact readiness. Confirm whether it is required by your destination and business process.
Next action: Review missing Email; confirm destination requirements and populate it where required.
| Source row | Record | Field | Value |
|---|---|---|---|
| 5 | 00125 | (empty) |
A preflight report checks the supplied file. Actual import success also depends on your destination configuration and live reference data.
Check your own customer export
Start with four free real-data analyses. No card required. Your source records stay in this browser; account history contains report summaries.
Analyse my own file Compare plans