Migration Extracts
After CCG processes your migration file, two result extracts are generated — a Success Extract and an Error Extract. Use these to verify successful migrations and identify records that need correction before re-attempting.
Overview
Migration extracts summarize the outcome of a completed migration job. CCG generates separate extract files for successful and failed records. Both extract files mirror the original migration file format, with an additional column appended to indicate the result.
| Extract Type | Additional Column | Purpose |
|---|---|---|
| Success Extract | ccgPaymentMethodId | Confirms successful migration and provides CCG IDs |
| Error Extract | errorDescription | Lists records that failed, with a reason for each error |
Success Extract
The Success Extract contains all records that were successfully migrated. Successfully migrated records include the assigned ccgPaymentMethodId appended at the end of each row. Records that failed processing in the same batch are also included but without a CCG Payment Method ID.
Store the ccgPaymentMethodId values from the Success Extract — these are the CCG identifiers for the migrated payment methods and will be required for future transactions.
Card example:
card_test_migration_file_20240625-153549_completed_20240625.csv
Bank Account example:
bank_account_test_migration_file_20240701-095200_completed_20240701.csv
Error Extract
The Error Extract contains all records that were not successfully processed. Each row includes an errorDescription column appended at the end of the line, describing why the record failed. Common causes include:
- Wrong formatting or incorrect field types
- Invalid or missing compulsory information
- Duplicate customer or payment method
After reviewing the error descriptions, correct the affected records and resubmit the file.
Card example:
card_test_migration_file_20240625-153549_error_20240625.csv
Internal Processing Notes
- Extracts are generated at the end of the full migration pipeline: after Customer Creation and Payment Method reconciliation.
- For Card migrations, reconciliation against Stripe is required before the Success Extract is finalized.
- For Bank Account migrations, ACH reconciliation runs before the extract is produced.
- Extracts are placed in the merchant's designated Azure Blob Storage container upon completion.
- CCG notifies the merchant via the agreed channel (email or SFTP) when extracts are ready.
Error Handling
If records appear in the Error Extract, review the errorDescription column for each failed row and take the following steps:
- Correct the data based on the error description.
- Create a new migration file containing only the failed records.
- Resubmit via ECG QuickConnect/SFTP.
FAQ
Q: What should I do with records in the Error Extract?
A: Review the errorDescription for each failed record, correct the issue, and resubmit as a new migration file.
Q: Not all records appear in the Success Extract — is that expected?
A: Yes. Only records that were fully and successfully migrated receive a ccgPaymentMethodId. Records that failed will appear in the Error Extract instead.
Q: How long are the extract files retained?
A: Retention policy depends on your CCG configuration. Contact your CCG integration manager for details.
Q: Can I automate ingestion of the extract files?
A: Yes. Extract files are deposited to your Azure Blob Storage container and can be consumed programmatically once the migration job status reaches COMPLETED.
Integration Checklist
- Migration job status confirmed as
COMPLETED - Success Extract downloaded and
ccgPaymentMethodIdvalues stored - Error Extract reviewed and error descriptions noted
- Failed records corrected and resubmitted (if any)
-
ccgPaymentMethodIdvalues mapped to merchant-side payment method identifiers