Native cloud documents and exports

Understand portable exports and why a cross-provider move can retain the original.

Some cloud files are native editing documents rather than ordinary downloadable byte files. A transfer to another provider needs an exported representation that the destination can store.

Google document exports

Native Google documents export into supported portable formats such as PDF or XLSX. The exported file is a representation of the source at transfer time. It is not a live editing link and does not recreate the full Google editing environment in the destination provider.

Check the resulting format before using it in an App or another workflow. A spreadsheet export and a PDF export serve different purposes. The transferred file may not preserve every editing feature, comment, sharing permission, or revision from the native original.

Move behavior

When a native source is exported across providers, Strive retains the original native source even if you selected move. It reports that retention in the job outcome. This avoids treating a successful export as proof that deleting the editable original is safe.

Do not infer that the destination and original will remain synchronized. Editing the Google document afterward does not update the exported file. To capture later changes, deliberately export or import a new version and review its impact on downstream data.

App imports

Importing a supported exported document into an App creates an independent managed snapshot. The App processes that captured representation, and its extraction evidence refers to the captured bytes. It does not continuously follow the native source.

If retaining editable originals matters for your process, record which provider item is authoritative and which portable export was used for processing. Use import into Apps for the snapshot lifecycle and evidence for the distinction between current source files and retained evidence.