SaaS portability is the ability to retrieve and use the required information and behavior from a hosted application in another arrangement. A record export is one component of that ability. It does not itself recreate the application, its configuration, or the process that operates through it.
A service can offer a convenient export while leaving relationships, attachments, history, permissions, or operational decisions to separate mechanisms. Portability assessment begins by defining what must remain usable when the original tenant is no longer available.
The export has a declared scope
Salesforce’s CLI bulk export runs a SOQL query through Bulk API 2.0 and writes records to a file. This establishes a specific record-extraction mechanism. It does not establish that one command retrieves every artifact needed to leave a Salesforce deployment.
An exit manifest should list required records, attachments, history, metadata, configuration, and relationships separately. Each item needs a retrieval method and a destination interpretation. Items absent from the export must remain visible as gaps.
The source population also matters. A successful query can return exactly the records requested while omitting records that the exit requirement should have included. Technical completion and scope completeness are different checks.
Relationships must survive the move
A set of readable files can still be difficult to use if identifiers no longer connect related objects. An invoice needs a customer relationship; an attachment needs its associated record; a history entry needs enough context to explain the change.
A representative reconstruction should follow a complete business record across those relationships. Counts alone cannot show whether the destination can answer the questions the business expects to ask.
Preserving identifiers and documenting mappings can support that reconstruction. The required mapping depends on both services. An open file format removes one parsing barrier without resolving every semantic difference.
Behavior may need to be rebuilt
Configurations, approval rules, extensions, integrations, and role assignments implement behavior beyond stored records. A replacement can provide a different way to achieve the same outcome, but that mapping needs an explicit decision.
A fit assessment should distinguish essential outcomes from incidental details of the old interface. Reproducing every screen can retain unnecessary complexity; omitting an unusual approval path can remove a required control.
Unfinished work adds a transition problem. A case already in progress needs an agreed destination state, responsible operator, and treatment of actions completed before cutover. Importing its current fields might not recreate its pending obligations.
Rights and practical capability are separate
Contractual exit provisions, retention periods, export limits, and service access require examination for the particular agreement. A technical export demonstration does not establish a contractual right, and a contractual right does not demonstrate a usable export.
The operating plan also needs identities, integration changes, archive access, and the time required for reconstruction. These dependencies can affect how long the original service must remain available during transition.
Exit cost should be revisited as configurations, data volume, and integrations change. A demonstration made before substantial customization describes an earlier dependency, not the current one.
Portability is a tradeoff to evaluate
Provider-specific capabilities can offer useful functionality while increasing replacement work. The decision is whether the benefit justifies an evidenced dependency and whether that dependency can be reduced where it matters.
A bounded exit rehearsal should retrieve the required artifacts, reconstruct a representative record, and complete a representative transaction in the intended destination. It should record omissions and manual work. That result gives a decision maker a concrete portability claim with a defined scope, instead of treating the presence of an export button as proof of independence.