Abstract: A method and system for migrating transactions, such as bill payment transactions, between payment modules and/or payment processors. Each payment object is set up with payment information input to a payment module and results in one or more transactions. During a selective migration, each transaction is treated separately, based on a state of the transaction. A transaction that has either not been yet submitted, or has been completed can be migrated directly, while a transaction that is in some state of processing is iteratively migrated as it completes processing.

Abstract: Systems and methods for migration between payment processors. A user sets-up payments with a financial institution using a client module (e.g., a personal finance manager). The client module sends the transaction data to an entity such as a bank OFX server and receives a first transaction identifier for use when making transaction requests. A migration module can initiate a migration process from the bank OFX server to an independent OFX server. The migration module can cancel payments at the bank OFX server and reconfigure on the independent OFX server. The migration module stores a second transaction identifier received from the independent OFX server. When the user subsequently makes a manual payment or updates payee information, the migration module switches the first transaction identifier with the second transaction identifier, and before forwarding to the independent OFX server.