Appearance
Data Migration
Data Migration supports controlled onboarding of existing records and balances into Pinkapple ERP. It is intended for administrators and implementation teams, not for normal day-to-day corrections after go-live.
Use migration screens only when moving an organisation from previous records, spreadsheets, another system, or an opening-balance exercise into Pinkapple ERP.
Workspace Reference
| Workspace | How Users Reach It | What Users Usually Do There |
|---|---|---|
| Data Migration | Administration -> General Setup -> Data Migration | Review migration state, load migration batches, manage catch-up activity, and confirm go-live readiness. |
| Import Engine | Platform import workspaces where available | Validate and submit structured import files for supported records. |
| Accounting, Loans, Deposits, Shares, Wallets, Inventory, And Other Service Workspaces | Service-specific setup and operations screens | Reconcile migrated records against live module views before go-live. |
| Reporting | Reporting and Accounting reports | Compare imported balances with approved source records and sign-off totals. |
What Data Migration Helps Manage
Data Migration helps administrators manage:
- Migration readiness.
- Migration batches.
- Imported balances or records.
- Catch-up activity.
- Reconciliation checks.
- Trial balance or balance sheet comparisons where applicable.
- Final readiness before users begin live operations.
Migration Overview
The overview area is used to check the migration state and determine whether the tenant is still in migration mode, ready for catch-up, or ready for live use.
Use this area to confirm that migration work is deliberate and controlled before users begin normal operations.
Typical migration step order is:
- Clients.
- Shares.
- Deposits.
- Loans.
- Inventory opening stock.
- TB / BS.
- Reconciliation.
- Catch-up.
- Lock or go-live completion.
Inventory Opening Stock
Use the Opening Stock migration step when the organisation must load opening warehouse stock balances as of the migration date.
This flow is intended for:
- approved opening stock snapshots
- stock imported from spreadsheets or a previous system
- one-time migration of starting inventory value and quantity
It is not intended for normal receipts after go-live.
For the detailed warehouse-specific import flow, see Inventory Opening Stock Migration.
Migration Batches
Migration batches group imported records or balances so they can be reviewed, validated, and reconciled together.
Good batch practice:
- Keep batches focused by module or migration stage.
- Use clear descriptions.
- Review validation results before accepting a batch.
- Do not mix unrelated records in one batch if it makes reconciliation harder.
Catch-Up Activity
Catch-up activity is used when operational movement must be brought forward from the migration snapshot date to the go-live position.
Use catch-up carefully. It should bridge the migration period, not replace normal transaction processing after go-live.
Reconciliation
Migration reconciliation checks whether imported balances and records agree with the approved source records. Review differences before allowing users to rely on the migrated data.
Common reconciliation checks include:
- Opening balances.
- Customer or member balances.
- Loan, deposit, share, wallet, stock, and accounting totals where applicable.
- Trial balance and balance sheet comparisons.
- Exceptions that need correction or sign-off.
Go-Live Readiness
Before go-live, confirm:
- Required migration batches are loaded.
- Validation exceptions are resolved or approved.
- Reconciliation differences are understood.
- Opening balances agree with signed-off records.
- Users understand when migration mode ends and normal processing begins.
Common Mistakes
- Using migration screens to correct live operational mistakes.
- Importing balances without reconciling totals.
- Mixing test and approved migration data.
- Running catch-up without agreeing the snapshot date.
- Allowing users to transact before migration differences are resolved.
Good Practice
Treat migration as a controlled implementation phase. After go-live, process corrections through the relevant business module so approvals, audit history, and financial effects remain clear.