Systems and methods for data migration

One or more non-transitory computer readable media containing computer executable instructions configured to perform a method comprising:

• (a) importing legacy data from a legacy application into a new system by storing the legacy data in a legacy database separate from data native to the new system;
• (b) independently maintaining, at the new system, (i) a first balance for a particular patient account in the legacy database, and (ii) a second balance for the particular patient account in a native database that stores data native to the new system;
• (c) generation an interface configured to allow a user to view both legacy data and data native to the new system, the interface including (i) information of the legacy data that is associated with the particular patient account, and (ii) one or more interface elements configured to allow the user to perform limited actions with respect to the particular patient account associated with the information;
• (d) receiving input corresponding to engagement of one of the user interface elements configured to perform limited actions with respect to the particular patient account associated with the information;
• and
• (e) in response to receiving input corresponding to engagement of one of the user interface elements configured to perform limited actions with respect to the particular patient account associated with the information, automatically updating both the first balance in the legacy database and the second balance in the native database while maintaining the independence of such balances by (i) modifying the first balance in the legacy database causing the first balance to have a first value, and (ii) modifying the second balance in the native database that stores data native to the new system causing the second balance to have a second value different than the first value.

A method comprising:

• (a) importing legacy data from a legacy application into a new system by storing the legacy data in a legacy database separate from data native to the new system;
• (b) independently maintaining, at the new system, (i) a first balance for a particular patient account in the legacy database, and (ii) a second balance having a first value for the particular patient account in a native database that stores data native to the new system;
• (c) generating an interface including (i) information of the legacy data that is associated with the particular patient account, and (ii) one or more interface elements configured to perform limited actions with respect to the particular patient account associated with the information;
• (d) receiving input corresponding to engagement of one of the user interface elements configured to allow the user to perform limited actions with respect to the particular patient account associated with the information;
• and
• (e) in response to receiving the input, automatically updating both the first balance in the legacy database and the second balance in the native database while maintaining the independence of such balances by modifying the first balance and the second balance to cause the second balance to have a second value different than the first value.