Migrate > Take the first steps after WebSphere Commerce migration > Migrating from a previous payment implementation
Migrate WebSphere Commerce Payments Multipayment Framework to v7 (compatibility mode)
Use WebSphere Commerce Payments Multipayment Framework in compatibility mode. By using compatibility mode, you can continue to use cassettes; however, we will not use the Payments subsystem. Consider using the WCPayments plug-in with cassettes instead of using the WebSphere Commerce Payments Multipayment Framework in compatibility mode.
Before you begin
Before migrating Payments, ensure that you have addressed the following considerations:
- All prerequisite software has been migrated or updated.
- You can access the previous version of the Payments and WebSphere Commerce databases.
- Migrate Payments database
The Payments database tier migration script (migratepaymentsdb) collects database information to determine the version, release level, and database type. The script then runs the appropriate pre-migration steps. It updates the Payments Schema to the WebSphere Commerce Payments, v7.0 level. Based on the version and release, the script runs the Payments data migration command for the Payments Framework and IBM cassettes, and any installed third-party cassettes. The required tables for third-party cassette are copied to the migrated database, however, the cassette might not be fully functional until it is redeployed or reinstalled.
- Migrate the Payments application
Select an appropriate migration path depending on the machine topology.
- Post Payments application and database tier migrating steps
In this step you define the host name and port number of the Payment server, you also specify whether to use SSL.
Next topic:
Migrate to the WCPayments plug-in
Related concepts
Payments subsystem architecture