Moving from Parapluie
Prepare existing records for a future controlled import.
Current migration status
The new workspace is built in Laravel and runs independently from WordPress. A production importer has not been implemented yet. The existing Parapluie workflows inform the module structure and future mapping.
Prepare your source records
- Identify the company that owns each source record.
- Inventory employees, departments, locations, stock, tasks, and customer balances.
- Resolve duplicate identifiers and missing relationships in an export copy.
- Keep the original export and source IDs for comparison and reconciliation.
Planned import process
The planned process maps fields, validates company ownership and relationships, runs a dry import, and compares record counts and financial totals before approval. A repeatable import should preserve legacy IDs and avoid duplicate records.