Dashboard
Prepare bCommerce import files or API payloads without database connectivity.
Load / Refresh Schema Definition
Loads the included tables/fields export and foreign-key export into Smart Import PostgreSQL.
Create Migration Project
SaaS Administration
Create tenants and review account plans.
| Tenant ID | Company | Plan | Status |
|---|
Autonomous AI Migration
Detect entities, propose mappings, calculate the sequence, simulate the migration, and surface only decisions that need review.
AI Decisions
| Type | Source | Target | Confidence | Reason | Status |
|---|
Start or Resume a Migration
Upload files or connect read-only to the system the customer is leaving. Connections are for periodic migration/cutover runs, not continuous synchronization.
Where is your data coming from?
Source Connection
Select What to Migrate
Migration Blueprint
Understand readiness, remaining questions, template coverage and the complete migration recipe.
Migration Questions
Technical errors are grouped into business questions. Answer once and store the answer as migration knowledge.
Migration Recipe
Migration Intelligence Library
Global connector templates are separate from tenant-specific and migration-specific knowledge.
| Connector | Template | Maturity | Current Version |
|---|
Connector Coverage Matrix
Support Escalations
| Project | Issue | Type | Status | Created |
|---|
Production Operations
Queue long-running work in background workers so users can leave and return later.
Notifications
Schema Registry
| Table | Fields | FK Out | FK In | Self-Service |
|---|
Admin Exposure
All schema tables remain known internally. Admin decides which tables users can select.
| Table | Group | Enabled | Self-Service | Admin Only | Method |
|---|
Self-Service Import Wizard
Reusable Mapping Profiles
Once a source is mapped successfully, save the mapping and recognize future files automatically.
| Name | Signature | Uses |
|---|
Preflight Validation
Catch data errors before any API call. Records with errors stay blocked; clean records remain ready.
| Table | Row | Field | Severity | Error | Value | Action |
|---|
Bulk Preflight Corrections
Download the errors CSV, fill the correctedValue column, then upload it here.
Admin Validation Rules
Add business rules on top of the reference schema.
| Table | Field | Rule | Severity | Config | Action |
|---|
Sequence Rules
Foreign keys come from the offline reference structure. Disable sequence enforcement only when a relationship is system-resolved, external, lookup-only, or otherwise not required before create.
| Child | Column | Parent | Parent Column | Enforce Sequence | Resolution |
|---|
Admin API Endpoint Registry
Every reference table can have its own API configuration. This controls live import only; the reference schema remains offline.
| Table | Self-Service | Configured | Endpoint | Action |
|---|
Configured API Endpoints
| Table | Enabled | Method | Create Endpoint | Mode | Batch | Lookup | Update |
|---|
Sequential API Import
Uses the exact same canonical dependency sequence as exported files. Tables execute one after another; records/batches inside each table also execute sequentially.
Failed Uploads / Correction Queue
Successful records stay imported. Only failed or unresolved records appear here for correction and retry.
| Table | Source Row | Type | Error | Status | Retries | Action |
|---|
Bulk Failed-Record Corrections
Download the failed CSV, fill correctedPayload, and re-upload it.
Resolved bCommerce IDs
Shows business/source IDs mapped to target IDs returned by the bCommerce API. These are used automatically in downstream dependent records.
| Table | Source Field | Source Value | bCommerce Target ID | Source |
|---|
Change-Only Import Detection
Compare prepared records with the last successful snapshot and avoid re-uploading unchanged data.
| Table | Business Key | Change Type |
|---|
Reconciliation
Compare source, prepared, imported, failed, and unresolved records.
Post-Import API Verification
Verify successful API imports through configured lookup endpoints. No database connection is used.
| Table | Target ID | Status | HTTP |
|---|
Monthly Trial Balance
Step 16 — Migration Complete
This is the final step after verification and reconciliation have passed.
Before calling the migration complete
Confirm that the production import has finished, failed records have been resolved or intentionally excluded, API verification is complete, and reconciliation passes.
For an Initial or Refresh migration, save the locked Migration Recipe for the next cutover run. For a Final migration, retain the migration report and audit history.