Organizations using legacy Thrinacia Atlas now have a clearer path to new Thrinacia Fabric. Over the past two weeks, we made our Atlas-to-Fabric migration workflow operational and validated it against existing Atlas installations and clients, with over 300+ legacy platforms already migrated. This update also expands payment gateway support and improves campaign management, onboarding, checkout and performance.
Atlas-to-Fabric migration is operational
Our migration workflow transfers the core data organizations need to carry their platform history into Fabric. This includes users, profiles, roles, addresses and organizations; campaigns, categories, managers, rewards and shipping rates; and comments, updates, website pages and policy content.
It also transfers contributions and historical Stripe and PayPal transaction records for reporting and reconciliation, along with supported campaign images, media, portal settings and connected campaign accounts.
The workflow includes planning and post-migration audit tools. Passwords, active subscriptions, webhooks and payment credentials receive special handling to protect account access and prevent duplicate billing. These items are reviewed as part of each migration. Each migration now typically takes 1-2 hours per platform, depending on the amount of data that needs to be transferred.
Expanded payment gateway support
Fabric now supports additional payment gateway configurations and embedded checkout capabilities. New tools help administrators configure credentials, check operational readiness and manage webhook registration. Checkout amounts display in each campaign’s configured currency.
One-time and recurring payment capabilities are handled separately, allowing organizations to add payment options without disrupting their existing recurring-payment setup.
More control over campaigns
Administrators can now choose the exact order of featured campaigns. The new Featured Order section under Campaigns offers drag-and-drop and arrow controls, with the saved order reflected on the public homepage.
Campaign administration is also faster for platforms with large databases. Server-side pagination and more scalable queries improve campaign lists, while new settings let administrators control results per page and the number of visible pagination links. Archive actions now require confirmation, campaign status and public routing have been corrected, and continuous campaigns can remain active after reaching their funding goal.
Better performance and content display
Public campaign listings now have a configurable page size and cleaner pagination. We also improved image loading and optimization across listings, rewards and campaign descriptions.
Migrated reward descriptions render more consistently, with improvements to HTML and media handling, duplicated markup, content overflow and embedded images.
Easier user onboarding and checkout
A new CSV import workflow lets administrators add users and invite them to set up their accounts securely, without assigning passwords manually. Password-reset expiration is configurable, and administrator searches perform better with large migrated user databases.
We also improved campaign creator onboarding, configurable checkout return URLs, and the handling of guest and registered contributors. Fixes to contribution totals, currency presentation and completed-payment associations help keep contributor and investor records accurate.
Localization and developer improvements
Public translation overrides now appear without a frontend rebuild. Organizations can tailor wording for their Fabric instance while continuing to use standard language packages. Default and fallback language handling has improved, and branding, typography, footer content and public text remain independently configurable.
For teams building custom frontends, Fabric now displays API base URLs and relevant endpoints alongside API-key management. Scoped API keys, REST APIs, webhooks and MCP integrations continue to support custom applications.
Platform reliability
Behind the scenes, we improved database connection handling, stale-transaction recovery, portal-setting saves and frontend builds. Customer Git access is scoped to the relevant repository, and controlled SSH and restart permissions support frontend development. Centralized updates also better protect customer customized frontends.
Planning a move from Atlas? Contact the Thrinacia team to discuss your installation, migration scope and the checks needed before moving to Fabric.