Without know specifics kinda hard to know what to recommend but you’re probably going to need a basic structure of properly backing up your dumps from system A, build a python script to convert the schema of system A to the schema of system B and properly store a backup of your new files to be uploaded to system B. Depends on how complicated you wanna make the process.

If you’re starting from scratch, you’re basically the trailblazer here. Is your company giving you a budget or a team to build the workflow?

Use dbt, host it on whatever they got (vSphere, cloud VMs, w/e) or schedule it the same way their “Devops” or “CICD” pipelines are orchestrated. Makes it easier if you wind up having a bunch of workers move data in parallel during the migration window or if you need to do a rolling refresh of the destination for validation or something.

If you can get access to the source database, query the INFORMATION_SCHEMA views (select * from information_schema.columns) to get the data types of the fields in the source system. Same for the destination it sounds like, but once you have the columns and tables present in both systems you can probably start mapping it easily or chatbots probably do OK at it.

ctrl+c then ctrl+v

I would start by documenting the schemas (data types and optional fields). Then use shell scripts to transform or join any data to be ingested to another system. Not sure what you’re working with so it’s hard to give any more concrete advice.

rclone and rsync maybe?