well, if there are several versions , then anyhow the data has to kept somewhere; for different version you may have to add an attribute,a column, to identify the data version ; have that column included in clustered key.

but the point is that who is going to own the data.

Does this version process has to be live ? In a live environment you can't move the records, when there is a lot,and a user is on the front.

If it's a request process then you can have job running for each request.

To save the back end loader time ,If it's millions of row , then check if SCD works for your business environment; this might save a lot , if it suits your business.and for newer versions you may have fewer data to go forth and may be a lot less to roll back.