Superblocks migration

Migrate from Superblocks to UI Bakery

Keep building with visual low-code. Bring your internal apps to UI Bakery with Enterprise SSO and your choice of Cloud or self-hosted deployment.

Move the workflows your team depends on, from admin panels to approval queues. Start with one app and build a migration plan around your data, permissions, and developers' everyday work.

Discuss your Superblocks migrationExplore the low-code builder

Migrate from Superblocks to UI Bakery with your low-code workflow in mind

Your team should be able to keep changing a query, adjusting a screen, or adding an approval step in a visual editor. UI Bakery brings that development approach to applications connected to your existing systems.

Build and maintain apps visually

Assemble screens with drag-and-drop components, connect SQL queries and APIs, and configure actions. Add JavaScript for custom business logic. Use AI assistance where it helps while continuing to edit and maintain your app through the low-code experience.

Bring your identity and access requirements

Connect your identity provider with Enterprise custom SSO. Define role-based access and use audit logs to support your governance requirements. Include the people who build, manage, and use your apps in the access model.

Choose where the platform runs

Use UI Bakery Cloud for managed hosting, or self-host the platform on infrastructure your organization controls. Choose the deployment model that fits your data connections and operating requirements.

Keep the editor at the center of development

In UI Bakery's low-code experience, developers work directly with components, data connections, and actions. A support console, inventory screen, or approval queue remains something your team can inspect and modify visually.

UI Bakery offers low-code and AI-only as separate development experiences. Choose low-code for your migration and test the work that follows the first release: changing validation, debugging a query, or updating an approval rule. Include your expectations for low-code support and product change notifications in the Enterprise discussion.

Explore the low-code development experience

SSO and governance belong in the migration plan

UI Bakery Enterprise supports custom SSO through SAML, OpenID Connect, and OAuth 2.0. Team and Enterprise plans include role-based access control and audit logs. Review the configuration with your IT team before moving production users.

Use the pilot to test sign-in with your identity provider and verify permissions for each user role. Check restricted actions, application access, and the audit events your organization needs. Enterprise pricing is tailored to your requirements; request a quote that includes your deployment model, developers, users, and support needs.

Review plans and Enterprise featuresRead the security documentation

Cloud or self-hosted: choose your operating model

RequirementUI Bakery CloudSelf-hosted UI Bakery
HostingManaged by UI BakeryInfrastructure your organization manages
Data connectivityPlan approved connections from the hosted platformPlan connections within your infrastructure and network policies
OperationsUI Bakery manages platform hostingYour team owns upgrades, monitoring, backups, and recovery
Custom SSOEnterprise configurationEnterprise configuration

Confirm connectivity, security requirements, and operational ownership before starting the pilot. Explore self-hosted UI Bakery.

Move one proven workflow at a time

  1. Map your existing apps

    List active apps, owners, data sources, custom code, automations, and permissions. Identify dependencies and the workflows that need to move first.

  2. Build a representative pilot

    Choose an app with a real data connection and a restricted write operation. Recreate its screens and actions, then test SSO and your intended deployment model.

  3. Validate behavior and maintenance

    Compare query results, business rules, and access controls. Ask a developer to make a realistic change after the app works. Test scheduled jobs separately.

  4. Roll out in stages

    Use the pilot to estimate remaining work. Agree on owner sign-off, cutover, and rollback. Assign each production job to one platform during the transition.

Superblocks migration questions

Can I import my Superblocks apps directly?

Plan for rebuilding and validating the applications. Existing SQL, API contracts, and business rules may be reusable; UI bindings, application state, permissions, and workflows need adaptation. Discuss any applicable migration tooling with the team.

Do my databases need to move?

Often you can retain the databases and replace the application layer. Validate each connection and network route. Assess any data stored in platform-managed services separately.

Can UI Bakery help with the migration?

App migration and custom development services are available through Enterprise. Bring your app inventory to discuss implementation scope, responsibilities, and pricing.

How long will migration take?

The pilot gives you a basis for estimating. Complexity, integrations, permissions, and testing affect effort as much as app count. Build the rollout schedule around your required transition date.

Bring your first Superblocks app

Share the workflow, your SSO requirements, and your preferred deployment model. Talk to UI Bakery about a migration pilot that preserves how your team builds and maintains internal apps.

Discuss your Superblocks migration