Processing at Cut Over

The go-live migration of open balances must only be done after trading has been closed in the client’s old system. There should be NO trading, and no accounting journals created in the old system once these steps commence. The client must be aware of this and either place a block in the system to prevent accidental journals or ensure all staff are aware of this.

The entry of receipts/payments can complicate the first few bank reconciliations in the new system. Where possible, any payments/receipts that will appear in a bank statement on or after go-live should not be processed in the old system, and instead, should be delayed and entered as soon as go-live transacting commences. This includes batch ABA payments that are prepared in advance. Any ABA batch payments, that will not be paid out of the bank before go-live should NOT be prepared in the old ERP. This will incorrectly affect the closing bank balance that will be migrated to Odoo. The bills should be taken across as open bills and the ABA payments prepared after go-live.

Whilst it is always the preference that all trading ceases, if there is any physcial activity occuring during the migration e.g. customer deliveries out, incoming deliveries from suppliers, these should be noted and then entered into Odoo after the go-live migration has been completed.