Alpine users have a deadline to preserve their team's work: noon New York time on October 31, 2026. After that, the service closes and customer data deletion begins, according to Alpine's official announcement.
Start with a usable backup. Choosing the next tool can follow once you know which documents, tasks, discussions, and assets you need to keep.
This guide covers a practical preservation plan and a narrower next step for teams whose saved material could become a business website. SiteKick CMS can help with that website project. Your team's collaboration and task-management needs deserve a separate migration decision.
What Alpine has announced
Alpine's October 1 announcement directs existing users to export through their settings or contact the support address listed in the announcement for help. It also says lifetime-access customers will receive a full refund without requesting one.
Treat the export deadline as the end of access. There is no promised grace period for retrieving work after the shutdown.
Alpine combines documents, tasks, forum discussions, chat, and AI features. The preservation checklist below is general migration advice, rather than a guarantee that Alpine's export includes every item or retains its original behavior.
Step 1: Make an inventory with your team
Ask each project owner to identify what the business needs to keep. Review:
- Documents, project briefs, meeting notes, and reusable business copy.
- Tasks, owners, due dates, dependencies, and open commitments.
- Discussions and decisions that explain why work was done.
- Uploaded images, attachments, and linked files.
- Shared links, access permissions, and important integrations.
Separate active work from reference material. Assign someone to verify each project's archive and someone to carry its outstanding commitments into the next system.
Respect the permissions and ownership attached to client and team material. A file being available to export does not make it appropriate for public publication.
Step 2: Request the export while you still have access
Sign in to Alpine and use the export options available in your account settings. If you cannot find them, or cannot confirm that an export covers an important project, contact Alpine support before the deadline.
Save the original downloads securely before you rename, edit, or reorganize them. Keep an additional backup in another location your team controls.
The shutdown notice does not specify export formats or promise a complete recreation of the workspace in another product. Check the actual files you receive before deciding how they can be imported elsewhere. Do not assume a document export also includes task assignments, attachments, comments, or conversation history.
Step 3: Check that your backup is useful
A completed download is only the start of verification. Open representative files from each important project and compare them with the original workspace.
For example, check whether a client brief still has its images, whether a project plan retains its dates and owners, and whether a key decision makes sense without the surrounding discussion. Record missing items while you can still return to Alpine or ask support for help.
Some links may point back to the hosted service. Save the underlying material where permitted, and identify references that will need updating after the move. Confirm that your colleagues can open the archive using the access arrangements you intend to keep.
Step 4: Choose a destination for each kind of work
Different parts of a workspace may need different homes.
| Material you need to keep using | What to evaluate in a destination |
|---|---|
| Internal documents and decisions | Search, permissions, editing, and durable backups |
| Open tasks and project commitments | Ownership, dates, status, and team handoff |
| Discussions and conversation history | Searchable archives and enough context to understand decisions |
| Public service descriptions, FAQs, and business articles | A website CMS with publishing and editing tools |
Test a small, representative import before moving the whole archive. Keep the original files available so you can check what changed or recover missing context.
What about Alpine's open-source code?
Alpine has published its source repository under an MIT license. The repository describes itself as a historical archive and states that maintenance, support, and security updates will not continue.
Keeping a copy of the code does not preserve your hosted account's data. Running it would be a separate technical project requiring a review of deployment, data restoration, security, and ongoing operation. Export your own material before making that decision.
When SiteKick CMS fits the next step
Some workspace content is useful beyond the team that created it. An approved service brief could become a services page. Answers to recurring customer questions could become a public FAQ. A collection of reviewed insights could become a business blog.
SiteKick CMS provides AI-assisted website creation, visual editing, and WordPress content management. For that kind of website project, use this workflow:
- Select material you own and have approved for public use.
- Remove private discussions, personal details, and confidential client information.
- Write a business brief describing your audience, offer, pages, and desired next action.
- Create and refine website pages using the approved material as a reference.
- Check facts, permissions, mobile layouts, navigation, and contact forms before publishing.
This is a content adaptation and website-building workflow. SiteKick CMS has no verified one-click Alpine importer and does not replace Alpine's complete internal collaboration workspace. Evaluate your document, project, and communication tools separately.
Frequently asked questions
How do I export Alpine data?
Alpine directs users to their settings or its support team. Confirm available formats and the contents of your own export while your account is accessible.
Can I wait until after the shutdown to download my work?
Do not rely on later access. Complete and check your backups before the announced deadline; deletion begins after service closes.
Does open source mean my workspace will keep running?
The published code is an archive. It does not keep the hosted service running or automatically recover your team's data on another host.
Can I move my Alpine content into SiteKick?
You can use suitable, approved content as reference material when building a website with SiteKick CMS. Import compatibility is unverified, and tasks, chat, permissions, and internal discussions need their own preservation plan.
Preserve the work, then decide what comes next
Give your team a checked archive and a clear plan for active projects. If part of that material is ready to become a customer-facing website, take it forward with a publishing workflow you can review and manage.
Turn your content into a website.
SiteKick is independent of Alpine and is not affiliated with or endorsed by it. Export availability and compatibility depend on your account and the files provided by Alpine.
