Method for a client to server deployment in a system via an online distribution platform wherein a plurality of clients (20, 21, 22) contributes to the server deployment comprising the following steps: a) Receiving a client software update and at least a part of an image of a server-side software update (20a, 21a, 22a) at each client of a plurality of clients (20, 21, 22) from an online distribution platform; b) Approving the software update (20b, 21b, 22b) by each client of the plurality of clients (20, 21, 22) to verify if a software update is necessary; c) Updating/installing software update (20c, 21c, 22c) on each client of the plurality of clients (20, 21, 22) and subsequent logging in into the server; d) Requesting a server deployment (20d, 21d, 22d) from the server by each client of the plurality of clients (20, 21, 22); e) Setting up, by the server, a waiting time to receive eventually more requests of server deployments (20d, 21d, 22d) from clients of the plurality of clients (20, 21, 22); f) Acknowledging the server deployment request (20e, 21e, 22e) of each client of the plurality of clients (20, 21, 22) by the server together with an individual sequential or random package number to each client (20, 21, 22); g) Sending, after expiration of the waiting time, a message of the total number of packages (20f, 21f, 22f) involved from the server to each client of the plurality of clients (20, 21, 22) participating in the upgrade; h) Dividing, by the clients of the plurality of clients (20, 21, 22), the at least a part of the image into equal and/or predetermined and/or random sized divided packages; i) Requesting, by the server, a respective package of the at least a part of the image of the server-side software update (20f, 21f, 22f) from each client of the plurality of clients (20, 21, 22); j) Transferring the respective package of the at least a part of the image of the server-side software update (20g, 21g, 22g) from each client of the plurality of clients (20, 21, 22) to the server; k) Combining, by the server, the packages received from each client of the plurality of clients (20, 21, 22); and l) Initializing of the deployment on the server. a) Receiving a client software update and at least a part of an image of a server-side software update (20a, 21a, 22a) at each client of a plurality of clients (20, 21, 22) from an online distribution platform; b) Approving the software update (20b, 21b, 22b) by each client of the plurality of clients (20, 21, 22) to verify if a software update is necessary; c) Updating/installing software update (20c, 21c, 22c) on each client of the plurality of clients (20, 21, 22) and subsequent logging in into the server; d) Requesting a server deployment (20d, 21d, 22d) from the server by each client of the plurality of clients (20, 21, 22); e) Setting up, by the server, a waiting time to receive eventually more requests of server deployments (20d, 21d, 22d) from clients of the plurality of clients (20, 21, 22); f) Acknowledging the server deployment request (20e, 21e, 22e) of each client of the plurality of clients (20, 21, 22) by the server together with an individual sequential or random package number to each client (20, 21, 22); g) Sending, after expiration of the waiting time, a message of the total number of packages (20f, 21f, 22f) involved from the server to each client of the plurality of clients (20, 21, 22) participating in the upgrade; h) Dividing, by the clients of the plurality of clients (20, 21, 22), the at least a part of the image into equal and/or predetermined and/or random sized divided packages; i) Requesting, by the server, a respective package of the at least a part of the image of the server-side software update (20f, 21f, 22f) from each client of the plurality of clients (20, 21, 22); j) Transferring the respective package of the at least a part of the image of the server-side software update (20g, 21g, 22g) from each client of the plurality of clients (20, 21, 22) to the server; k) Combining, by the server, the packages received from each client of the plurality of clients (20, 21, 22); and l) Initializing of the deployment on the server.