To my way of thinking, that is all the more reason to employ an approach of a single page with dynamic panel, as josephxbrick recommends. Just think of each state in your dp as its own page (or wizard step) Your “steps” or data from each step could progressively show up as user steps through the wizard. Each state in your dp would just have increasingly more information (or perhaps only the last step would show all this information. Alternatively, you could have 10 dp’s, one for each step. The point is, all data entered by the user would still be available as long as you are still on the same web page. Otherwise, you would end up having to pass a lot of data from page to page. If it is all text-based data (not images) then you can do this, but it will be limited and possibly less reliable.Consider the similarities of your repeaters/data and think about the minimum amount of data you could place in global variables and still have the experience reasonable.
Here is a recent thread I replied to with a “separate page and global variables” approach that could work for you. The basic idea is to create identical repeaters on each page you need them, in global variable(s) pass row identifiers (a number, char or brief alphanumeric that points to a specific row.) and the appropriate rows can be shown by removing their filters. If you have dynamic text entered on one page that you want to pass to another page that could be appended to a global variable.