Mendix is moving to git as well for their own teamserver versioning.
While it is also possible to use your own on-premise Git repository:
Common practice is to have a separated Development branch line for ongoing development and a maintenance branch line. Which are merged to the mainline at the end of each dev. sprint. Note that the best approach is to have a single development branch line, which is used by ALL developers. instead of having a separated development branch per developer, which is more common in code development.
I don't think there will be any difference in the impact. Mendix team server is also a SVN, which holds all history and changes. Same as a private GIT?
I think it might get easier, since the team-server is fully incorporated in Mendix studio.