Keep the records you already have
Preflight matches supplied fields against existing records. Differences need review; the migration workflow doesn't silently overwrite your workspace.
Agent-assisted data migration
Bring your data.
Your agent takes it from here.
Switching from another system? Working from spreadsheets? Give your existing files to Codex or another connected agent. It can map your fields, check the records and move them into Wholety.
Migration tools included in your one-month free trial
Legacy stock export.xlsx
| Row | Item | Quantity | Unit |
|---|---|---|---|
| 2 | COLA-12 | 1.50 | Cases |
| 3 | OAT-6 | 8.00 | Cases |
Agent maps the fieldsYou resolve uncertain facts
Ready for your review
- Product codes
- COLA-12, OAT-6
- Packaging
- 12 and 6 units per case
- Opening quantities
- 1.50 and 8.00 cases
The columns identify products, packaging and case quantities. Your agent can prepare a mapped preview for review.
Interactive example using a sample catalog. No files are uploaded and no account data is used. Connect your agent to check your own records.
Keep your files.
Let your agent map the move.
The agent works with the data you already have, then prepares it for Wholety's business fields. Keep your original files and review the proposed mapping before records are written.
The migration workspace can package your originals and instructions in one local download. Give the extracted folder to your connected agent; it reads your data, checks Wholety’s live fields and prepares the move.
Prepare your files for an agentAn existing system
Readable exports of products, partners, warehouses, stock and orders. Keep source references so you can trace each migrated record.
Spreadsheets and files
Excel, CSV and JSON with your own column names. The agent resolves fields, units, dates and currencies before sending the data.
No system yet
Start from the records you maintain today. Readable documents can provide data when the agent can reliably extract and verify the required fields.
Give it your files.
Review the mapping. Move in.
Connect your agent
Create your free account and connect MCP. In the migration workspace, choose your originals and propose a cutoff. Download the files and request together, then give the extracted folder to your agent. Read access is enough to plan and preview.
Set up the connectionCheck a real sample
The agent reads Wholety's current schemas and previews mapped rows. Missing references, duplicate codes, existing-record differences and account limits are flagged.
Migrate in batches
After the plan is agreed, enable write access. The agent creates records through the same business operations as your team and keeps a source-to-target ledger.
Reconcile the result
Export matching purchase and sales summaries to Excel and check saved import references against the agent’s ledger. Reconcile quantities and actual payments separately; completed batches and unresolved rows stay in the ledger so work can continue.
Follow an order
through the move.
An old document total can include tax and freight. Your agent keeps that source value, maps each amount to the right place and reconciles actual payment records separately.
Explore one example before you connect your own data. Purchase payable uses goods and discount; sales receivable includes tax. Neither is a payment receipt.
| Source field | Value | Wholety record |
|---|---|---|
| Goods amount | 20.00 | Goods amount |
| Discount | -2.00 | Order discount |
| Tax | 2.34 | Recorded separately |
| Freight | 10.00 | Separate shipping operation |
| Document total | 30.34 | Kept as a source reference |
| Actual date | Amount |
|---|---|
| 5.00 | |
| 7.00 |
- Purchase payable
- 18.00
- Recorded payments
- 0.00
- Amount needing payment evidence
- 18.00
No payment records were supplied. Zero recorded payments does not prove the order was unpaid; the agent keeps the amount to reconcile and never infers cash from a document total or closed status.
A local example with sample records. It does not read or write account data. Created orders, completed stock movements and actual payments are checked separately during your migration.
The details that make
a move trustworthy.
Flexible source data still needs clear business facts. The agent highlights what needs a decision and keeps a record of what actually moved.
Count the stock once
Choose current opening quantities or a replay of historical inventory. Purchase imports receive stock; importing the same stock again as an opening balance would double-count it.
Move actual payments, too
Historical order imports can include dated payment records. An order total or a closed status is never treated as proof of payment. Missing cost or tax information needs clarification.
Resume with evidence
Your agent saves normalized sources, target mappings and checkpoints in your Wholety account. Keep the original files as evidence. If a write result is uncertain, it checks the actual target records before continuing. The preview is a check, not an account-wide transaction.
Pause the work.
Keep the progress.
Your migration has a home in your Wholety account. Each saved source row stays connected to its target and the last checkpoint, so an Agent can reopen the task and continue from the evidence.
Compare current records in the dashboard, or give the saved task to your connected Agent. A changed amount stays a difference to resolve; it does not trigger another import.
Open your migration ledger- Source row
- Orders.csv:row-17
- Wholety target
- Not linked yet
- Source payable (CAD)
- 18.00
- Current target payable (CAD)
- Not checked
- Comparison
- Pending
- Payment completeness
- Unknown — no source payment evidence supplied
The source row is saved in the account. After an interruption, the Agent reads actual target records before deciding whether to continue.
Illustrative ledger. This example does not read your account or write any data. Only a new checkpoint saves a current comparison.
Keep going
after a connection drops.
A move can span many requests. Your team and connected Agent can recover a new purchase draft by its saved creation reference, then continue from the current order.
One purchase intent, one draft
The dashboard keeps a new draft’s original request before sending it. Your connected Agent can use the same creation contract. Repeating that original request returns the same order and goods.
Read the result first
After a lost response, find the current order first. The dashboard retains recovery after a reload; only a confirmed missing result permits the original creation to continue. Agents can look up the draft with read access.
Continue from the business facts
Historical orders retain their import references. Stock movements, shipping and payments each need their own checks; a recovered order is not proof that the whole migration has finished.
Start with your
own business data.
Your one-month free trial includes all features and 1 hour of consultation and assistance. Open the migration workspace to check capacity, choose your original files, name the move and suggest a cutover date. Download the originals and request in one local package, or give the files directly to your connected agent. It can help you choose current stock or historical replay before any records move.
A request to give your connected agent
Before you bring your data
Do I have to reshape every file myself?
No fixed source template is required. Your agent interprets your files and prepares the target fields. You still need enough reliable data for the intended Wholety operation; ambiguous or missing facts are surfaced for review.
What can I migrate?
The guided preview covers brands, warehouses, suppliers, customers, products, opening stock and historical purchase and sales orders with actual payments. Shipping information and document attachments use the other available MCP business operations. The agent checks the live schemas rather than assuming every legacy field has a target.
Can I keep current stock and import historical orders?
Decide the cutover first. Historical purchase import creates inventory, and historical sales import can fulfill against it. Replaying the same history and adding its full current stock would count quantities twice. The current history-import operations are not a separate archive with no stock effects.
How do I check the orders after migration?
Purchase and sales lists can export all matching saved order summaries to Excel, across pages. The file retains system IDs, recorded import references, saved amounts and the filters used. Long references remain text and permission-masked values stay masked. Your account’s migration ledger links saved source rows to target records and compares supplied amounts and payments; item lines, stock movements, actual payments and attachments need their own reconciliation.
What happens if I run the migration again?
Known imported orders appear as existing records for review. A matching source number links to an order; it does not prove every field agrees. Hidden records or multiple targets need clarification. If a write result is unknown, your agent reads the target state and reopens its saved ledger and checks current records before continuing, so it can resume without blindly replaying stock or payments.
Is this automatic for every old system?
The source needs to be readable by your agent. It handles the mapping and migration work through MCP, while you resolve ambiguous business facts and approve the intended changes. Capacity limits and the target system's business checks still apply.