---
title: Imports and Backups
description: >-
  Use Excel imports and tenant backups with preview, controlled restoration, and
  documented operational limits.
audiencia: Administrator | Superadministrator
roles: >-
  Administrator authorized in the company; Superadministrator for permitted
  platform operations
modulo: Company Administration
revision: '2026-10-19'
section: administrar-empresa
order: 30
sources:
  - CONTEXT.md
  - ARCHITECTURE.md
  - TESTING_GUIDE.md
  - Módulosydependencias.md
locale: en
---
# Imports and Backups

Excel imports and backups are operations bounded by company. Uploads have a preview and managed application; backups are tenant-specific, and restoration is controlled. No unconfirmed template, retention period, recovery point, or procedure is documented.

## Before you begin

- **Role:** use administrative authorization in the company. The Administrator configures the tenant; platform operations require permitted platform authorization.
- **Module:** Company Administration. The functional administration areas include Imports and Backups; any object you operate on through an upload remains subject to the applicable company and module rules.
- **Preconditions:** confirm the effective company, your active membership, and the operation’s objective. Prepare an Excel file whose contents belong to that company. Do not use the file to try to select or replace the tenant: the import company is derived from the session, never from the file.

The indicative paths are **Administration > Imports** and **Administration > Backups**. They do not presuppose undocumented columns, buttons, forms, or screen sequences.

## Import from Excel

Excel import has two confirmed phases: **preview** and **managed application**. The preview is for inspecting the upload before applying changes. Application takes place in the tenant context resolved from the session, not from an identifier in the file.

## Recommended workflow

1. **Limit the scope of the upload.** Identify the business data and its belonging to the active company. A value in the file cannot change the authorization context.
2. **Use the preview.** Review it before applying. It confirms the upload, not a universal set of validations, column template, or automatic correction.
3. **Apply in a managed manner.** Proceed when the content is as expected. The upload does not bypass tenant, module, membership, capability, or scope rules.
4. **Review the authorized result.** Confirm data using permitted functions and record actual relationships, not name similarities.

> **Synthetic example:** a file prepared for “North Company” is reviewed from that company’s session. Including a supposed identifier for “South Company” in the Excel file must not redirect the upload or grant access to its data; the effective context remains North Company.

### Import limits that must be preserved

The sources do not establish a template, maximum size, object coverage, replacement, deduplication, undo, or automatic rollback. They also do not confirm SQL execution. A rule only generates SQL when a physical field is associated and a dialect is configured; this does not imply automatic execution.

An import must not be treated as a substitute for connectors, metadata synchronization, or scans. Metadata retains its own model of Repositories, fields, snapshots, and schedule, and its connections or scans are not presumed to be available merely because an Excel file exists.

## Backups by company

GovFrame documents tenant backups and **controlled restoration**. A backup belongs to a company; restoration is not an unrestricted, automatic, or interchangeable action between companies. Define the company and objective; do not assume partial restoration, overwriting, duration, or retention.

There is a configuration for monthly backups that can be enabled. This does not confirm an active schedule or enabled production jobs: verify the authorized configuration and status before relying on it.

**Metadata snapshots** are not a tenant backup. Synchronization may retain versioned snapshots and a manual, daily, weekly, or monthly schedule. The effective schedule depends on the company; do not assume automation, scans, or restoration coverage.

## Expected result

The upload is reviewed with a preview and applied only in the company derived from the session. Backups and restoration are controlled tenant operations, without promises of undocumented capabilities, frequencies, or recoveries. Imports, snapshots, and operational backups are not conflated.

## References for further information

- [Modules and dependencies](/en/referencia/modulos-y-dependencias/)
- [Roles, capabilities, and scope](/en/referencia/roles-capacidades-y-alcance/)
- [Object model and relationships](/en/explicaciones/modelo-de-objetos-y-relaciones/)
- [How to read the relationship map](/en/guias/como-leer-mapa-de-relaciones/)