I may not know much about programming, but utilizing a relational DB I might be able to envision the following.
Optional Club DB; which presently has the ability to hold 5 clubs. By adding two additional fields which I'll name as follows;
1) Club that you are substituting;
2) Club that you are replacing;
Just a thought, I could be wrong.