Keeping your data portable

Netice delivers reporting into a destination controlled by your organization. Your warehouse tables or stored files can remain inputs to your own SQL and BI models. A transition to another ingestion process should preserve both the data and its meaning: report family, currency, dates, estimation methods and source lineage.

Destination ownership is separate from subscription terms. This guide covers technical handover planning; the terms of service govern the commercial relationship.

Capture the contract before switching writers

• Record the output table or file locations and the downstream models that consume them.
• Keep the Daily App Sales and Platform Finance field definitions with the handover.
• Record report currency, date or period coverage and the source families included.
• Preserve a snapshot before a new process starts replacing managed output.

Do not run two writers against the same output

Test the replacement pipeline in a separate table or prefix. Compare reporting scope, signed amounts, currencies and missing-value treatment before switching downstream consumers. Two independent writers refreshing the same location can overwrite one another’s results even when both individual runs succeed.

Retain source artifacts when required

Normalized rows do not preserve every provider-native column. If future reprocessing needs provider-specific fields, keep the relevant Raw Reports output and its report-family context, taking your own snapshots when needed. Raw managed files may be decoded, period-merged, recompressed and replaced; retain original provider downloads separately if your process requires byte-identical files. Provider retention limits still apply when downloading missing history later.

Finish the access handover

Once the replacement workflow is verified and scheduled, retire the old reporting schedule and revoke access that is no longer required through the source and destination providers. Check shared saved connections before revocation so unrelated active workflows are not interrupted.

For account or subscription changes, use Netice support. For a historical-data comparison, follow the rerun validation steps.