You can create the migration control account as a current liability account.
The Migration control accounts will be used to record the relevant debits and credits from their corresponding transactions in the new system.
For example, a customer balance debited in the new system accounts receivable would have a corresponding credit recorded in the migration accounts receivable account. Do you see where I am going with this?
If you’re a non-accounting person reading this, then you're recording how much your customer owes as a balance in the new system. And to adhere to the double entry accounting principle, every debit has to match with a corresponding credit. This means you have to put the credit somewhere. In this case the migration control account. Make sense?
The migration control account keeps a record of the balances from your old system at the time of the migration. The objective is to get the aggregated balance of the migration account to zero.
The notional ‘opening balances’ in your new system are recorded using a general journal. I strongly suggest you record in the general journal and in the working paper what this balance is. I mean the customer, and each of the underlying transaction IDs. I’m referring to the Invoice number.
I also suggest you create a classification you can add to each type of journal, i.e. ‘migration AR’. This will help you follow the trail of any discrepancies, and tell you what the journal was for.
A reliable accounts receivable migration journal would contain a debit and credit for each customer. So if you’ve hundreds of customers and open invoices you’d need to create a large journal. The good news is there’s an ‘Upload Journals’ import sheet in the Setup>Import Data section of your system.
If you're an accountant, you will have spotted I’m referring to the simple process of moving the unadjusted trial balance and the underlying transaction detail to the new system.
Also, you’ll understand why, and how over time when the closing trail balance is determined, the migration control account will be reduced to zero, and if it is not then how useful the detail in the migration control account will be in debugging the problem.
If you’re not an accountant, here’s a simple explanation:
So, you have an open and unpaid invoice in your old system. The payment for this invoice is received in your new system. The amount owed is in your new system. The migration control account maintains the integrity of the accounting relationship of the two transactions. (I promise you).
“What about aging debtors and creditors?”, I hear you whisper. You can run the aging reports in your old system, right? This is the map of what is open and needs to be transferred over. It also tells you what and to who you need to pay attention to.