Skool to Sparkforge Migration Guide

This guide moves your Skool community, courses, members, events, and automations into Sparkforge. Plan the migration during off-hours, back up everything first, and validate before turning Skool off.

Prep work

Inventory what you have

• Active members and their custom fields
• Courses, modules, videos, and resources
• Pinned community posts and discussions
• Scheduled events and recurrence rules
• Automations: welcome sequences, completion notifications, event reminders

Set goals

Decide why you're moving — better CRM, automation, unified platform — and prioritize the components you need live first. Members and active courses usually come first.

Back everything up

Export the member list, course content, and any community posts you want to preserve. Store the files securely before you touch Skool.

Export from Skool

• Members: In Members, use Export to download a CSV with names, emails, and custom fields.
• Courses: Save video links, descriptions, and resources for re-upload.
• Community content: Manually copy or export the posts and pinned content you need.

Import into Sparkforge

1. Members: Go to Contacts > Import Contacts. Map every field correctly during import.
2. Courses: Open the Courses section and create new courses. Upload videos, descriptions, and resources.
3. Community: Use the community tools to recreate discussions and pin essential posts via Featured Posts.

Rebuild community and courses

Channels

Recreate each Skool channel in Sparkforge. Set privacy and access levels to match. Invite members via email or unique invite links using Contacts > Send Email.

Course structure

Mirror Skool's sections and modules. Set per-course access permissions so the right members get the right content.

Roles and permissions

Assign Admin, Moderator, or Contributor roles. Configure permissions for channels, courses, and community features so the hierarchy carries over.

Events and automations

Events

Use the Sparkforge calendar to recreate scheduled events, including recurring ones. Set up email and SMS reminders to drive attendance.

Automations

Go to Automation > Workflows and rebuild Skool's automations: welcome messages, course completion notifications, and event reminders. Test each workflow with a sample contact before going live.

Validation

• Run end-to-end tests: join a channel, access a course, post in a discussion.
• Cross-check imported member counts and custom fields against the Skool export.
• Confirm event reminders and automation emails fire on schedule.

Train and transition

Train your team on Sparkforge's community management, course setup, and automation tools. Provide written SOPs. Run Skool and Sparkforge in parallel until you're confident, then back up Skool one last time and cancel the subscription.