Adobe Business Catalyst Source Data Export
Prepare existing Adobe Business Catalyst backup and export files for Next-Cart source data file upload.
Adobe Business Catalyst Source Data Export
Section titled “Adobe Business Catalyst Source Data Export”A complete Adobe Business Catalyst export gives Next-Cart the source files required by the selected migration path.
When to use this guide
Section titled “When to use this guide”Use this guide when:
- Adobe Business Catalyst is the Source Platform;
- Next-Cart shows source data file upload for Adobe Business Catalyst;
- you already have legacy backup files, site export files, CRM exports, or eCommerce data exports.
Prerequisites
Section titled “Prerequisites”Before you begin, confirm that:
| Requirement | Why it matters |
|---|---|
| Existing backup files | The hosted platform is unavailable, so data must come from files you already possess. |
| Site export package | Content and site files may be stored in a ZIP export. |
| CRM or customer export | Customer data may exist in a separate CSV export. |
| eCommerce exports | Product and order data may exist in separate CSV files. |
| File ownership approval | Legacy backups may contain personal and order data that must be handled securely. |
Data types to export
Section titled “Data types to export”| Data type | Required file or source | Notes |
|---|---|---|
| Site content | Site export ZIP, if available | May contain website assets and content files. |
| Customers | CRM or customer CSV export | Required if customer records are in scope. |
| Products | eCommerce product CSV export | Required if product catalog data is in scope. |
| Orders | eCommerce order CSV export | Required if historical order data is in scope. |
Before you prepare files
Section titled “Before you prepare files”Do not create empty replacement files. If a required legacy export does not exist, mark it as unavailable and contact support.
Create a folder such as:
source-exports/└── adobe-business-catalyst/ ├── site-backup/ ├── customers/ ├── products/ └── orders/Prepare the files
Section titled “Prepare the files”- Locate the Adobe Business Catalyst site export ZIP, if you have one.
- Locate CRM or customer CSV exports, if customer data is in scope.
- Locate eCommerce product CSV exports, if product data is in scope.
- Locate eCommerce order CSV exports, if order history is in scope.
- Place each file in the matching folder.
- Keep original file names where possible.
- Create a short notes file that lists which expected files are present and which are missing.
Organize the exported files
Section titled “Organize the exported files”| File type | Place it in |
|---|---|
| Site export ZIP | source-exports/adobe-business-catalyst/site-backup/ |
| CRM or customer CSV | source-exports/adobe-business-catalyst/customers/ |
| Product CSV | source-exports/adobe-business-catalyst/products/ |
| Order CSV | source-exports/adobe-business-catalyst/orders/ |
| Availability notes | source-exports/adobe-business-catalyst/ |
Expected result
Section titled “Expected result”You have all available Adobe Business Catalyst backup and export files organized for review and upload to Next-Cart.
Verify the export package
Section titled “Verify the export package”| Check | Pass condition |
|---|---|
| Existing files | Every file you intend to upload exists locally and can be opened or extracted. |
| File origin | Files come from Adobe Business Catalyst backups or exports, not manually reconstructed data. |
| Scope coverage | Products, Customers, Orders, and site content are present where they are in scope. |
| Missing-file notes | Any unavailable file is clearly listed before upload. |
| File integrity | ZIP files extract successfully and CSV files are readable. |
If the export is incomplete
Section titled “If the export is incomplete”| Issue | What to check |
|---|---|
| No backup files exist | The legacy data may not be recoverable from the discontinued hosted platform. Contact support before proceeding. |
| Site ZIP exists but data CSV files are missing | Upload the site ZIP only if requested, and note that customer, product, or order files are unavailable. |
| CSV files are corrupted | Look for another backup copy before upload. |
| Files have unclear names | Keep the files, but add a notes file describing the expected contents of each file. |
| Custom fields are present in unusual files | Preserve representative examples and confirm whether supported mapping can handle them. Use Custom Service only for the portion that remains outside supported handling. |
Next step
Section titled “Next step”| Goal | Go to |
|---|---|
| Upload the prepared files | Upload Source Data Files |
| Explain missing legacy files | Tickets |
| Define custom handling for legacy fields | Prepare Custom Service Requirements |