Plan a Database Migration
Identify all objects that touch a legacy database, tag them as migration targets, and export the list.
Before you start
| Who this is for | Architect, DBA, project manager |
| Role required | Editor or higher |
| Prerequisites | Application imported; application uses a legacy database (Oracle, DB2, SQL Server, etc.) |
Step 1: Map all objects that access the legacy database
Use the Data Call Graph scope to find all objects that read from or write to the legacy tables.
For each key table:
- Open the Data Call Graph scope.
- Select the table.
- Note the objects in the call graph.
See Map database access patterns.
Step 2: Tag migration targets
Tag all objects identified in Step 1 with a label such as migration-target or db2-to-postgres.
See Tag objects, transactions, and modules.
Step 3: Use the Modernization Advisor
Open the Modernization Advisor to see automated recommendations for your specific migration path (for example, DB2 to PostgreSQL, Oracle to MySQL).
Step 4: Export the migration target list
Generate a report to get a structured list of all tagged objects.
- Open the Report dialog.
- Select Data Sources > Relation between Objects and Data Sources.
- Export as CSV or XLSX.
Filter the exported data by your migration tag.
See Generate built-in data reports.
Next steps
Feedback
Was this page helpful?