You can combine In-Database Archiving with partitioning:
https://asktom.oracle.com/pls/asktom/asktom.search?tag=statistics-in-database-archiving#9537345800346657311 So it sounds like you could use this to do something similar to your current solution. Rows will still move between the partitions when you "delete" them though.
Would I move to it if you already have a working solution? Probably not. You'll have (significant?) rework for your application to move to it. The benefits would have to be large to outweigh this cost. Unless your current solution has other significant drawbacks, it'll take a while for In-Database Archiving to recoup the rework effort.
Would I consider it for a new table/application? Yes.
So the real question is:
What problems (other than "internal data movement") is the current solution causing you? And how do you expect In-Database Archiving to solve these?