Checklist: what do you own on a no-code platform, and what can you take away?

Direct answer

Ask four questions about your no-code app: whose account does it sit in, what data can you export and is the export complete, what logic and workflows can leave with you and what would have to be rebuilt, and who pays the plan. What a platform lets you export or transfer differs by platform and changes over time, so do not rely on general statements, including this page. Check the platform's current help pages and terms, and prove the answers with a real test export. This page is a checklist for your decisions and records; it makes no claim about any platform's features or terms, and it is not legal advice.

What you own and what the platform keeps

Think of a no-code app as layers, and check each one separately:

• Your data: the records your business puts in. Usually the layer you most want to be able to take with you.
• Your app design: screens, forms, page layouts and the way they are arranged.
• Your logic: rules, workflows, automations and formulas that make the app behave.
• The runtime: the engine that actually runs the app. On many platforms this stays with the platform.

Whose account the app sits in

If an agency or freelancer built the app, find out whether it lives in their workspace or in one your business owns. Look at the workspace or team settings and the list of owners and administrators. If the app is in their account, ask what the platform currently offers for moving an app or workspace to another owner, and whether any steps require both parties. The practical route may be a transfer, an invitation as owner, or nothing at all, and you should know which before you need it, not after. Record the answer in your account register.

Data export test

Do not wait for a crisis to find out whether an export works. Run one now and check it:

• Export the data using the platform's own export options and open the file
• Check that every table, record type and linked relationship you rely on is present
• Check that dates, numbers, long text and special characters arrive intact
• Check what is not included, such as uploaded files, user accounts and change history
• Store the export in a place your business controls and note the date

Logic and workflows

Data is usually easier to move than behaviour. Make a list of the rules and workflows the app runs, such as approvals, notifications, calculations and scheduled actions, and for each ask whether the platform lets you export it in a form another tool could read. In many cases the honest answer is that the logic must be described and rebuilt, so write it down in plain language now. A documented list of what the app does is worth having regardless of platform. See what documentation to receive with custom software for what to ask for.

Integrations and keys that live inside the platform

Connections to email, payments, accounting and other tools often hold keys or authorisations inside the platform's settings. List them all, note whose login each was authorised under, and check whether the keys could be reissued from the other side if you moved. A connection created under a developer's personal account can stop working when that account is removed.

Plan and billing owner

Check whose payment method pays for the platform plan and whose email receives the invoices and notices. If the plan lapses, the app may become restricted or unavailable according to the platform's own terms. Read what they currently say about non-payment and downgrades. Put the plan under a business payment method and a role mailbox, and add a renewal check to your calendar.

Signals it is time to move

Staying can be a perfectly good decision. Signs that it is worth looking at an alternative include limits you keep working around, needing something the platform does not support, a cost that no longer matches the value, or dependence on a single person who understands the setup. The comparison is set out in low-code versus custom internal tool, and the case of a spreadsheet or old database is in replacing an Access database or Excel macro app.

Where LATYNEX fits

LATYNEX can help you write down what your app does, run and review a data export, and, if a move makes sense, plan the rebuild as a custom application that your business owns from the start. We do not promise that a migration will reproduce the current behaviour exactly or that no data will be lost; that is checked during the work.

LATYNEX is not the right fit when staying is right: if the app does its job, you can export what you need and the plan is under your control, there is no reason to move. It is also not the right fit when the limit is on the platform's side, such as a transfer they do not allow or a term that restricts export, which is for the platform's support and, where contracts are involved, a qualified adviser.