- Consulting services
GitHub Migration Workshop
A 3-day, hands-on GitHub Migration Workshop equipping teams with strategies, tools, and repeatable processes for seamless VCS-to-Git transitions. Offers post-workshop office hours for ongoing support.
Standard GitHub Migration Workshop – Build Skills for Seamless Transitions.
InfoMagnus offers a 3-day, expert-led Standard Migration Workshop designed to give your teams the knowledge, tools, and confidence to migrate Version Control System (VCS) data to GitHub Enterprise. Combining hands-on learning with best practices, our sessions cover every step—from preparation to execution—to ensure a smooth, efficient, and repeatable migration process.
Who Should Attend:
– VCS Administrators
– GitHub Enterprise Administrators
– DevOps Engineers
Prerequisites:
– SSH client
– Git 2.7 or greater
– GitHub Enterprise Server account for all participants
Workshop Format:
– Duration: 9 hours total (three 3-hour live, instructor-led sessions)
– Delivery: Microsoft Teams with virtual slides and guided demonstrations
– Time Zones: U.S. and Global availability
– Participants: Up to 20 per session
What You’ll Learn:
– Documenting migration processes and considerations
– Cleaning up large binaries and consolidating branches
– Trimming version control history for performance
– Reviewing and selecting migration utilities
– Conducting migration dry-runs and issue resolution
– Creating repeatable playbooks for future self-serve migrations
Learning Outcomes
By the end of the workshop, your team will be able to:
– Develop a migration strategy tailored to your environment
– Prepare repositories for Git migration
– Execute migration dry runs with confidence
– Support full production migrations with minimal disruption
Post-Workshop Support:
Includes 8 hours of recurring office hours (expandable as needed) to keep momentum going, answer questions, and provide hands-on troubleshooting as your migration progresses.
With InfoMagnus, your migration journey starts with expertise and ends with a team capable of owning their transition to GitHub.