--- title: 'Alpine Is Shutting Down: Export Your Knowledge Before October 31' published_at: 2026-10-14T12:00:00Z author: Arthur Ketchel II tags: - Alpine - Data Portability - Local-First - Knowledge Ownership - Migration categories: - Knowledge Ownership - Migration content_class: problem_intent search_intent: problem_aware primary_keyword: Alpine shutdown secondary_keywords: Alpine export, Alpine alternative, Alpine data migration, local-first knowledge, portable Markdown topic_ids: alpine-shutdown, data-portability, local-first seo_title: 'Alpine Is Shutting Down: Export Your Data by October 31' meta_description: Alpine closes October 31, 2026. Export your workspace now, protect an untouched backup, and see how Phasoric's existing Markdown and document imports can help. excerpt: Alpine's October 31 shutdown is a reminder that our knowledge should outlast the services we use. Here's how to preserve your export now—and what Phasoric can and cannot import today. slug: alpine-shutdown-export-your-knowledge contentClass: problem_intent searchIntent: problem_aware primaryKeyword: Alpine shutdown secondaryKeywords: - Alpine export - Alpine alternative - Alpine data migration - local-first knowledge - portable Markdown topicIds: - alpine-shutdown - data-portability - local-first seoTitle: 'Alpine Is Shutting Down: Export Your Data by October 31' metaDescription: Alpine closes October 31, 2026. Export your workspace now, protect an untouched backup, and see how Phasoric's existing Markdown and document imports can help. canonicalUrl: socialImageUrl: schemaProfile: standard faq: [] targets: [] canonical_url: https://phasoric.com/blog/alpine-shutdown-export-your-knowledge markdown_url: https://phasoric.com/blog/alpine-shutdown-export-your-knowledge.md --- # Alpine Is Shutting Down: Export Your Knowledge Before October 31 On October 1, 2026, Alpine founder Caleb Meredith [announced that Alpine is shutting down](https://www.alpine.inc/). The company brought documents, tasks, chat, discussions, search, and AI into one workspace. Its team invested years in an ambitious vision, and we respect the work they did—including their decision to [release Alpine's source code](https://github.com/alpine4work/alpine) under the MIT license as the service comes to an end. For anyone who used Alpine to organize projects, collaborate, or preserve decisions, the immediate question is practical: **how do you make sure your work survives the shutdown?** > **Action required: Alpine says existing users have until noon New York time (12:00 p.m. EDT) on Saturday, October 31, 2026, to export their data.** After that, the service will shut down and Alpine will begin permanently deleting customer data. Export from your Alpine account settings, or contact [support@alpine.inc](mailto:support@alpine.inc) for assistance. [Read Alpine's announcement](https://www.alpine.inc/). ## Save your Alpine export first. Choose your next platform second. You do not have to finish a migration before Alpine closes. You **do** need to obtain and safely retain your data before the export deadline. We recommend taking these steps now: 1. **Request or download the official export.** Sign in to Alpine, visit your settings, and look for the data export option. If you cannot access it or the export fails, contact Alpine support while the service is still operating. 2. **Keep an untouched original.** Store the complete download in at least two places under your control, ideally including one copy outside the service you plan to migrate into. Do not edit the only copy of the archive. 3. **Check what you received.** Inspect whether the export includes your important documents, attachments, tasks, discussions, chat records, and relevant metadata. Do not assume every feature is represented in an export merely because the download completed. 4. **Record what is missing.** If essential records, files, or relationships are absent, ask Alpine support about them before October 31. Preserve the original archive and a record of the export date. 5. **Plan the migration after the data is safe.** Test a subset in your next workspace, review the result, and only then proceed with the rest. An export's format and completeness matter. A collection of readable Markdown files is quite different from a proprietary data archive; even when text transfers successfully, permissions, comments, relationships, and task state may require separate attention. The essential distinction is this: **the deadline to export is not necessarily the deadline to migrate**. Once you have safely retained an adequate export, you can evaluate your options without racing a service shutdown. ## Why local-first knowledge ownership matters Alpine's closure highlights a broader question about how we store valuable knowledge. The most useful part of a workspace is often not its interface. It is the history of decisions, project context, research, working documents, and relationships accumulated over months or years. That value should not disappear because a subscription ends, a vendor changes direction, or a hosted product shuts down. This is one reason we built [Phasoric](https://phasoric.com/) around a **local-first, portable Markdown foundation**. Local-first is about more than working without a network connection. Combined with open, readable file formats and deliberate backups, it gives people more control over how their knowledge is stored, accessed, recovered, and moved. In Phasoric, you can keep a vault local to your device or explicitly configure supported synchronization through Dropbox, Google Drive, GitHub, or Phasoric Hosted. Markdown remains the primary portable format for notes, rather than requiring another application to decode a proprietary notebook just to read your writing. There are important boundaries to that promise. Local browser storage is not a substitute for a backup; devices fail and browser data can be cleared. Hosted vaults still depend on an online service for hosted access. And no Markdown-based tool can automatically reproduce every workflow, comment system, or collaboration feature of another product. **Ownership means having a practical exit path—not pretending that any platform or storage medium is infallible.** Regular backups, readable exports, and the ability to verify what you have retained all matter. ## Moving useful knowledge into Phasoric today We want to be clear about what exists today: **Phasoric does not currently offer a dedicated Alpine importer.** We have not validated Alpine's official export format as a one-click migration source, and we are not claiming to recreate Alpine's chat, forums, task management, permissions, or collaborative history. However, Phasoric's existing [Migration Studio and import options](/import) can help with content that is already in a supported format. - **Markdown folders:** Bring in supported Markdown or plain-text notes and attachments. If your Alpine export contains these files, extract a working copy of the archive and inspect the files before attempting an import. - **Supported PDF documents:** Import supported PDFs as document-derived Markdown, with extraction limitations. Keep the original PDFs, especially when layouts, images, scans, or embedded material matter. - **Other existing migration paths:** Phasoric also supports specific export workflows for Obsidian, Evernote ENEX, Notion Markdown exports, Inkdrop, and NotesHub. These are source-specific options—not a promise that an arbitrary Alpine archive can be imported by selecting a different provider. Migration Studio is designed to preview file inventories, links, attachments, collisions, and potential problems before committing supported content. Keep your untouched Alpine export regardless of the result. If your export is in an unsupported format, **do not discard it and do not assume conversion will be lossless**. Keep the archive until you have established a reliable way to read the records you need. ## Need help with a custom migration? Every workspace is different. You may primarily need to preserve documents, or you may have important project discussions, task relationships, and historical context that require more careful handling. If the existing Phasoric import paths do not match your export, [contact the Phasoric team](/help) to discuss custom migration assistance. Let us know the format of your export, approximately how much data it contains, and which types of records matter most. We can discuss the scope and available options; a custom migration is not an existing one-click feature. For security, please avoid sending confidential workspace content or complete archives through an initial support request. We can first determine what information is needed to evaluate the migration. ## The knowledge should outlast the tool This is not a criticism of Alpine or its team. Products evolve, companies change direction, and even carefully engineered software may eventually close. Alpine has given customers notice and an opportunity to export; users should take advantage of it. The more important long-term lesson is that **your knowledge should remain useful even when the application that helped create it is gone**. If you are an Alpine user, export your data before **October 31, 2026, at noon New York time**. Preserve an untouched copy. Then decide which tools will help you work with that knowledge next. [Explore Phasoric's current import options](/import) or [reach out about migration assistance](/help). *Phasoric is independent of Alpine and is not affiliated with or endorsed by Alpine or Work Technologies Inc.*