When a reminder gets lost in the inbox: Why clean migration matters
An invoice is overdue, no one followed up, and replies get lost in an overflowing e‑mail inbox. Such everyday scenarios become particularly critical when a company changes its operations or its receivables platform. Errors during the data transfer result in incorrect balances, lost payment histories, or unnecessary reminder dispatches. This playbook shows step by step how to securely and controllably transfer open items, customer master data, payments and history between on‑prem Debentra instances.
Quick overview: Process in five phases
- 1) Preparation & inventory
- 2) Export of source data
- 3) Consistency checks & ID mapping
- 4) Minimal downtime & final delta reconciliation
- 5) Re‑import, validation and follow‑up work
Preparation & inventory: Clarity before starting
Before you move data, create a complete inventory of the relevant objects: customer profiles, invoices, open items, payments (including partial payments and installment plans), dunning runs, and all related documents such as PDF originals or payment receipts. Also define which fields must be transferred (e.g. customer number, invoice number, amount, due date, status) and which format will be used (CSV/UTF‑8, JSON, ISO‑8601 for dates, ISO‑4217 for currencies).
Export of source data: Order and formats
Export data in a fixed order so that references can be traced later:
- Customers → master data, contacts, addresses
- Invoices → line item data optionally, totals, due dates
- Open items → links to invoices and customers
- Payments → payment amount, payment date, used payment references
- Partial payments / installment plans → installment amount, due sequence, allocations
- Documents & history → transcription files, PDF receipts, comment threads
Use structured exports (JSON) for complex relations where possible; CSV is suitable for tabular bulk exports. Pay attention to UTF‑8 encoding and consistent date formats (e.g. 2026‑11‑12T09:00:00Z).
Consistency checks & ID mapping: Establishing integrity
Before importing into the target instance you should perform several checks:
- Sum reconciliation: Do balances per customer match between the source data and the export files?
- Referential integrity: Do all open items have an assigned invoice and a customer entry?
- Duplicate check: Are there duplicate invoice or customer numbers?
- Currency and tax identifiers: Do ISO codes and tax keys match those in the target instance?
ID mapping is central: create a mapping table that associates source data IDs with the new target IDs or a persistent external_id field. Recommended approach:
- Keep the original IDs as external_id in the target instance to make history and audit trails easy to follow.
- Create a mapping CSV/JSON: source_id → target_id or source_id → external_id.
- Define rules for name conflicts (e.g., identical customer numbers): automatic suffixes, consolidation, or manual review.
Minimizing downtime: parallel operation and delta sync
The goal is to keep productive interruptions as short as possible. Established strategies:
- Staging migration: perform a full rehearsal run in a staging environment.
- Parallel operation: run both Debentra instances in parallel for a while before the cutover — all transactions continue to occur in the source system.
- Delta export: perform a delta export shortly before the final switch that contains records added or changed since the last full export (new invoices, payments, status changes).
- Write lock for final phase: during the final sync window, lock write access in the source system or explicitly enable a maintenance mode to avoid inconsistencies.
- Batching and transactions: import large volumes of data in controlled batches and use transactions on the target side to allow rollbacks in case of errors.
Re-import: order, idempotence and conflict strategy
The correct order for re-import reduces errors:
- Customers (including external_id)
- Invoices
- Open items / billing status
- Payments (including allocations to invoices and partial payments)
- Installment plans and partial payment runs
- Documents and history
Idempotence is important: every import attempt should be repeatable without creating duplicate records. Practical measures:
- Use external_id to detect already imported records.
- Implement conflict rules: skip (if already present), overwrite (for newer timestamp values), or merge (combine data).
- Log all actions and produce an audit log with the mapping table for later reviews.
Post-import validation: reconciliation and approval processes
After the import, the following checks are necessary:
- Spot checks: compare invoice PDFs, amounts and payment entries with the source system.
- Balance check: total balances per customer must match the inventory.
- Open items: no invoices without assigned line items or payments.
- Check dunning status: avoid automatic sending of payment reminders without manual approval; Debentra leaves control with the user.
Tests, rollback and documentation
Run at least one full test in a staging environment. Document migration steps, used export files, mapping tables and any manual corrections. Plan a rollback strategy: if the target instance is inconsistent, restore the original state from a backup and analyse the root cause of the error.
Practical checklist (brief)
- Create inventory and define export formats.
- Perform a complete export (customers → invoices → payments → documents).
- Perform integrity checks and create mapping table (external_id).
- Staging import and validation; tests for idempotence.
- Plan delta sync, define maintenance window, perform final import.
- Post-import reconciliation and manual approval of reminders.
- Keep documentation and rollback script ready.
Why Debentra helps here
Debentra is designed as a self-hosted solution to preserve data sovereignty and controlled processes. The software centralises customers, invoices, open items and payments on your own infrastructure and documents traceability and history. In the PRO edition Debentra reduces manual matching work during re-import, while the PREMIUM edition offers additional integrated accounting features for later review and reconciliation tasks. With automated workflows, the approval of payment reminders always remains with the user — an important control after migration.
In short: focus on control, transparency and auditability
A migration of open items is not a technical fine-tuning project but a process that requires data consistency, traceability and clear procedures. With a strict sequence, consistent export formats, a clean IDs mapping and a delta sync for minimal downtime you significantly reduce risks. Test fully in a staging instance, log every step and keep the approval processes for dunning and reminders under your control.
Act now: Choose the appropriate Debentra edition for your migration requirements and plan the secure transfer of your open items. Choose an edition
Next step
Try Debentra yourself
Central overview and process control for open items and payments with full data sovereignty; reduces manual matching work (PRO) and enables integrated accounting (PREMIUM); selectable installation and licensing models.