After some additional searching I found a set of steps the following is my updated version.
Code:
#In this example we will export a calendar called "Client Enforcement calendar" from one user to
# another user and name it "Client Enforcement" in the destination account.
#
#
# * Export the calendar "Client Enforcement calendar" from user DepartingUser:
#
# Source/Destination may be of the form
# https://SPCC Email Server/home/accountname/IT%20Vacation-Leave
#
curl [-k] -u admin-user 'https://ServerName:7071/home/DepartingUser/Client%20Enforcement%20calendar?fmt=ics' > ClientEnforcement.ics
#
# I needed the k option due to a Cirts issues.
#
#
#
# * Adjust all the meeting organizer addresses. If you don't do this, the destination user will see the appointments, but can not edit them.
cat ClientEnforcement.ics | sed 's/DepartingUser@/NewOwner@/g' > ClientEnforcement-Dest.ics
#
#
#
# * Create empty calendar in destination user account.
su - zimbra -c 'zmmailbox -z -m NewOwner createFolder --view appointment /ClientEnforcement'
#
#
#
# * Import modified ical data into new calendar.
curl [-k] -u "admin" --data-binary @ClientEnforcement-Dest.ics 'https://ServerName:7071/home/NewOwner/ClientEnforcement?fmt=ics'
#
# Have new "Owner" re-send the Share to those that should have access.
#
# Note I have setup a non owned share by creating a Resource for calendars that should not be owned by a person
# as of now it appears to work
The use of a Resource as the Owner mitigates the need if the next person to be the "Owner" should leave.