nope it sure won't. You have two viable options there.
1. You use a STAGING table in your database along to store the information.
PROS - Its in a database, you can pull and store whatever you want at whatever stage in the process. You can then move the data to its permanent home.
CONS - This needs some form of identifier to say John doe is really John doe next time he comes to the page, that way you can pick up where he left off. If you have a user system in place (login before you fill out the form type of thing), no problem. If not, the only real way to do this is using IP, or cookies.
2. Second option is using cookies. If they come to the form, and you noticed that have 1-3 pages filled out, shoot them to the 4th page to continue
PROS - Don't have to dink with a database, information is stored on the users computer.
CONS - A user clears their cookies, they have to start over. Or if they don't accept the use of cookies browser side.
You're on the right track... My suggestion, figure out which info is required and which is not and give a ONE PAGE registration form. After all, I'm not sure what this is for, but if you have 6 pages worth of questions... SHIT, my health insurance application for my entire family had only about 10 questions... FIX IT UP!!!