1. Introduction
This article describes how to prepare and import the information needed to perform an initial data migration in Consuman Evolution using Excel files.
Each entity has its own import template. Additionally, some entities have supplementary files for incorporating specific information, such as Additional Data or Stock Points.
The templates included in this instruction manual are:
- Assets.
- Additional Asset Data.
- Components.
- Structures.
- Tasks.
- Supplies.
- Additional Input Data.
- Stock points.
- Suppliers.
- Additional Supplier Information.
- Programs.
- Readings.
- Users.
- Additional User Data.
- Parameters.
For an initial migration, it is recommended to import the Parameters first, since different entities use them as a reference and the import Excel files do not allow them to be created automatically.
2. General considerations
Before starting a migration, consider the following conditions.
2.1. Use the Consumer Evolution templates
Always use the template corresponding to the entity you wish to import.
Do not add, delete, modify or change the position of the columns included in the file, unless specifically instructed.
When a template includes formats, drop-down lists, or predefined settings, keep them.
2.2. Create the related information beforehand
When a column refers to another entity or a parameter, that information must be previously registered in Consumer Evolution.
For example, before importing an Asset that has an assigned Criticality, Cost Center, or Type, those Parameters must exist.
Importing does not automatically create new parameters, even if the user performing the process has permissions to create them.
2.3. Respect the names used in relationships
To link entities from Excel files, use the corresponding entity name, unless the template expressly indicates another identifier.
For example:
- To link an Asset to a Location, use the Location Name.
- To associate a Component in a Structure, use the Component Name.
- To link a Task, use its Name.
- To identify a User, use their Email.
2.4. Use Unique Names
When the entity requires a unique Name, first verify that there are no duplicate records.
When necessary, modify the Names before importing to be able to identify each record unambiguously.
2.5. Complete dates
When a template includes a date and time column, use the predefined format in Excel.
Example: 8/10/2026 1:00:00
Do not modify the column format.
2.6. Fields with multiple values
When a column allows more than one value to be reported, separate the values using a semicolon.
Example: MECHANICS; ELECTRICITY
Apply this condition only to fields that accept multiple values.
2.7. Required fields
[PENDING VALIDATION AND IMPLEMENTATION]
A uniform visual criterion for identifying mandatory fields within Consuman Evolution templates has yet to be defined.
Once implemented, include in this section the visual reference used to distinguish them.
2.8. Importing existing records
As a general rule, imports are geared towards creating new records.
There are specific cases where a new import modifies existing information:
- Additional Data: If the record already has a value for the same field, the new value replaces the previous one.
- Stock points: If a configuration already exists for the same combination of Input and Warehouse, the imported values update the existing configuration.
3. How to perform an import?
To perform an import:
- Enter the corresponding module.
- Access the option from which the records are managed.
- Select Import .
- Download the corresponding template, if necessary.
- Complete the file respecting its structure.
- Select the file you want to import.
- Run the import.
- Review the result of the process.
- Correct the file and re-import it if errors are reported.
If an error is detected during processing, a partial import is not performed. The reported errors must be corrected first, and then the process must be run again.
Errors are displayed in the Import Logs section.
The user performing the process must have the appropriate permission to create the entity. The operation is recorded in the system audit log.
Figure 1 – Import Example
[INSERT IMAGE]
Include a screenshot of Consumer Evolution showing the Import button and the window used to select the file.
4. Prepare and import the information by module
4.1. Entities
4.1.1. Assets
Use the Assets.xlsx template to import Consuman Evolution Assets.
This same file can be used to create:
- Locations.
- Warehouses.
- Teams.
- Tools.
In Consumer Evolution, all these records are part of the Assets entity and are differentiated by their configuration.
Key: Asset identifier code. This is optional; it can be left blank and the system will generate a default code. If provided, it must be unique.
Name: Asset Name. Must be unique, whether it's Equipment, Location, Warehouse, or Tool.
Type: Parameter that classifies the Asset. It must have been previously created in Consumer Evolution.
Asset type: Indicate the primary type of record: Equipment or Location.
Tags: Tags that you want to associate with the Asset. If more than one is entered, separate them with a semicolon ( ; ).
[REVIEW] Criticality: Criticality parameter corresponding to the Asset. It must already exist.
Cost center: Associated cost center. If completed, the parameter must already exist.
Accounting account: Associated accounting account. If completed, the parameter must already exist.
Notes: Free text with additional information about the asset.
Location: Name of the immediately above location. Do not include the full tree path. For the first level, this can be left blank.
Is it a tool? Indicate Yes when the Equipment corresponds to a Tool.
Manage stock: Indicate Yes when a Location should function as a Warehouse.
Additional Asset Data
Use the Additional Data Assets.xlsx template to complete the Additional Data for Assets that have already been created.
The import does not create new Additional Data fields.
If an Asset already has a reported value for the same Additional Data, the new import replaces the existing value .
Entity: For this file, complete with Active.
Name: Enter the exact name of the asset to which you wish to assign the additional data. Do not use the key. The asset must exist in the system.
Dynamic field: Specify the exact name of the Additional Data previously configured for Assets. Importing does not create new Additional Data.
Value: Complete when the Additional Data is of type Text, Number, Drop-down list, or Multiple choice. If it allows multiple values, separate them with a semicolon (; ).
Check: Complete only when the Additional Data is of type Check. The template accepts TRUE and FALSE values.
Date: Complete only when the Additional Data is of type Date and Time. Use the predefined format in the template, for example 8/30/2026 1:00:00.
Figure 2 – Example of the Assets file
[INSERT IMAGE]
Include a screenshot of Assets.xlsx showing different levels of Location, Equipment, and Warehouse. Highlight the columns Name, Asset Type, Location, Is a Tool, and Manages Stock.
4.1.2. Components
Use the Components.xlsx template to import the Components that will be used in the Asset Structures.
Key: Component identifier code. This is optional and can be left blank.
Type: Allows you to classify or group the Component. This is optional. If completed, you must specify the exact name of a previously created Parameter.
Name: Name that identifies the Component. It must be completed and cannot be repeated between Components.
[INSERT IMAGE]
4.1.3. Structures
Use the Structures.xlsx template to import the Structures that define the Components corresponding to each Equipment Type. The Equipment Types and Components included in the template must already exist in the system.
Equipment Type: Specify the exact name of the equipment type to which the structure belongs. This parameter must already exist.
Component: Specify the exact name of the component you wish to add to the structure. The component must already exist.
Parent Component: Indicate the name of the component immediately above it in the structure. When the component is at the first level, leave this column empty.
To complete the file, please take into account the following considerations:
- The Equipment Type must have an empty Structure before performing the import.
- Repeating the same Component within a Structure is not allowed.
- The Parent Component must be loaded in a previous row of the same Excel file before incorporating its Child Components.
- The component is loaded one at a time per row. This Excel file does not use the semicolon (;) separator to include multiple components in the same cell.
Figure 3 – Example of the Structures file
[INSERT IMAGE]
Include a screenshot of Structures.xlsx showing a top-level component and one or more child components, highlighting the Team Type, Component, and Parent Component columns.
4.1.4. Tasks
Use the Tasks.xlsx template to import Tasks that can later be used in Programs and Work Orders.
In Consuman Evolution, the Task Type determines how feedback is received during execution. For this reason, the Task Types used in Consuman are not directly migrated as Parameters.
Key: Task identifier code. This is optional and can be left blank so the system can automatically generate a key.
Name: Name that identifies the Task. It must be unique and cannot be repeated between Tasks.
Type: Indicate the Task Type according to the information that must be recorded during its execution. The template includes a list of supported Types.
The main types are:
- By time/date: to record the completion of the Task by Date and Time.
- Single answer: when only one answer must be selected.
- Multiple response: when several answers can be selected.
- By reading: when the Task is used to record a measurement.
- By check: when it is necessary to confirm the completion of the Task.
- By location: when the Task is fed back through a Location.
Responses: Indicate the available responses for Single Response or Multiple Response tasks. Responses must already exist as parameters. When more than one response is required, separate them with a semicolon (; ).
Specialty: Indicate the specialty required to perform the task. If completed, the parameter must already exist.
Notes: Free text with supplementary information for the assignment.
Figure 4 – Example of the Tasks file
[INSERT IMAGE]
Include a screenshot of Tasks.xlsx showing examples of different Task Types and, where applicable, the upload of Responses separated by semicolons.
4.1.5. Inputs
Use the Insumos.xlsx template to import the supplies used in maintenance and inventory management.
Key: Input identifier code. This is optional and can be left blank so the system can automatically generate a key.
Name: Name that identifies the Input. It must be unique and cannot be repeated among Inputs.
Category: Parameter used to classify the Input. It must already exist.
Subcategory: Parameter used to perform an additional classification within the Category. If completed, it must already exist.
Unit of measure: Indicate the unit of measure in which the input will be managed or consumed. The parameter must already exist.
Purchase Unit: Indicate the unit in which the supply is acquired. If completed, it must already exist.
Conversion factor: Indicate the relationship between the unit of purchase and the unit of measure. Complete with a numerical value when both units are different.
For example, if an input is purchased in 20-liter containers and is consumed by the liter, complete the conversion factor with 20.
Notes: Free text with supplementary information from the Input.
Manage stock: Indicate Yes when you want to control the stock and movements of the Input in the Warehouses using vouchers.
Amount: Indicate the economic value corresponding to the Input.
Currency: Indicate the currency corresponding to the reported amount.
Date of amount: Indicate the date corresponding to the reported value. Use the predefined format in the template, for example 8/30/2026 1:00:00.
Exchange Rate: Indicate the exchange rate used for the amount when working with a currency that requires conversion.
Additional Input Data
Use the Additional Data template inputs.xlsx to complete the Additional Data for Inputs that have already been created.
The import does not create new Additional Data fields.
If an Input already has a reported value for the same Additional Data, the new import replaces the existing value .
Entity: For this file, complete with Input.
Name: Indicate the exact name of the input to which you wish to assign the additional data. The input must exist in the system.
Dynamic field: Indicate the exact name of the additional data previously configured for inputs.
Value: Complete when the Additional Data is of type Text, Number, Drop-down list, or Multiple choice. If it allows multiple values, separate them with a semicolon (; ).
Check: Complete only when the Additional Data is of type Check. The template accepts TRUE and FALSE values.
Date: Complete only when the Additional Data is of type Date and Time. Use the predefined format in the template, for example 8/30/2026 1:00:00.
The Import of Additional Data validates that both the entity and the dynamic field already exist and that the entered value corresponds to the configured Data Type.
Stock points
Use the Punto-Stock.xlsx template to import or update the stock levels defined for each Input and Warehouse.
Input: Specify the exact name of the input. The input must exist and have the Manage Stock option enabled.
Warehouse: Specify the exact name of the warehouse where you want to configure the stock point. The warehouse must already exist.
Minimum Stock: Indicate the minimum quantity you wish to keep available.
Order Point: Indicate the quantity from which the replacement of the Input should be considered.
Maximum Stock: Indicate the maximum quantity defined for the Input in the Warehouse.
To complete these values, the following conditions must be met:
- The minimum stock must be less than the maximum stock.
- The Reorder Point must be between the Minimum Stock and the Maximum Stock, and may coincide with one of them.
- The three values cannot be equal.
- Negative values are not allowed.
- If one of the three values is completed, the other two must be completed.
- If a configuration already exists for the same Input and Warehouse, the imported values replace the existing ones.
- It is not permitted to leave gaps by importing values that are already registered.
The current version of the import identifies the record using the Input column and not using the Input Key.
Figure 5 – Example of the Inputs file
[INSERT IMAGE]
Include a screenshot of Insumos.xlsx and another of Punto-Stock.xlsx showing the main fields used to register an Insumo and configure its stock levels.
4.1.6. Suppliers
Use the Suppliers.xlsx template to import the Suppliers used in Consumer Evolution.
Key: Supplier identification code. This is optional and can be left blank so that the system can generate a key automatically.
Type: Parameter used to classify the Supplier. If completed, it must already exist.
Name: Name or business name that identifies the Supplier.
Street: Street corresponding to the Supplier's address.
Number: Number corresponding to the address.
Floor: Floor corresponding to the address, when applicable.
Neighborhood: Neighborhood corresponding to the location of the Supplier.
City: City corresponding to the address.
Postal code: Postal code corresponding to the address.
Province: Province or state corresponding to the address.
Country: Country corresponding to the address.
Primary number: Provider's primary phone number.
Secondary number: Provider's alternate phone number.
Email: Supplier's email address.
Tax Identification: Supplier's tax identification number or code.
Notes: Free text with additional information from the Supplier.
Additional Supplier Information
Use the Additional-Data-suppliers.xlsx template to complete the Additional Data for Suppliers that have already been created.
Entity: For this file, complete with Supplier.
Name: Indicate the exact name of the supplier to whom you wish to assign the additional data.
Dynamic field: Indicate the exact name of the additional data previously configured for suppliers.
Value: Complete when the Additional Data is of type Text, Number, Drop-down list, or Multiple choice. If it allows multiple values, separate them with a semicolon (; ).
Check: Complete only when the Additional Data is of type Check. The template accepts TRUE and FALSE values.
Date: Complete only when the Additional Data is of type Date and Time. Use the predefined format in the template.
If the Supplier already has a reported value for the same Additional Data, the new import replaces the existing value .
Figure 6 – Example of the Suppliers file
[INSERT IMAGE]
Include a screenshot of Suppliers.xlsx showing the columns Key, Type, Name, contact information and Tax Identification.
4.2. Operability
4.2.1. Programs
Use the Programs.xlsx template to create Programs and load their Activators.
The template includes a sheet called Programs, where general information is entered, and different sheets where details corresponding to each Activator Type are incorporated.
A single Program can contain details on different Trigger sheets. The Name column included on these sheets allows you to determine which Program each detail belongs to.
Importing is intended for creating new programs. It should not be used to modify existing programs or to add details to a program that has already been created.
Type: Specify the Program Type. The parameter must already exist.
Name: Indicate the name that will identify the Program.
Manager: Indicate the User or Users responsible for the Program. If more than one is indicated, separate them with a semicolon ( ; ).
Automatic Work Order Generation: Indicate Yes when the program should automatically generate work orders. Otherwise, indicate No.
Grouping: Select the criteria to be used to group the information when generating automatic work orders. Use one of the options available in the template list.
Additional tasks: Complete according to the desired configuration for the Program.
Each Program defined on this sheet must have at least one associated detail on one of the Activators sheets. Importing allows the same Name to appear on different sheets and groups all those details into a single Program.
Time-based trigger
Use the Time Trigger sheet when the execution of a Task depends on a time interval.
Name: Name of the Program to which the detail will be associated.
Asset: Name of the Asset for which the Task is to be planned.
Component: Name of the component on which the task will be performed. Leave blank when the task is performed directly on the asset.
Task: Name of the task you want to plan.
Repeat every: Amount of time between executions.
Time Unit: The unit used to define the repetition. For this trigger, Day, Month, or Year are used.
Base date: Date used as a reference for calculating future executions.
Date until: Date until which the detail will be valid, where applicable.
Is it external?: Indicate if the task will be performed through an external work order.
Supplier: Indicate the Supplier Name when the execution is external.
Activator by Predefined Days
Use the Predefined Days Trigger sheet when the Task needs to run on specific days of the week.
Name: Program Name.
Asset: Asset Name.
Component: Component Name, where applicable.
Task: Task Name.
Repeat every: Amount used to determine how often the schedule repeats.
Time Unit: Use Week, Month or Year, as appropriate.
Sunday / Monday / Tuesday / Wednesday / Thursday / Friday / Saturday: Indicate the days on which the Task should be performed.
Base date: Reference date for starting planning.
Date until: Expiry date, where applicable.
Is it external?: Indicate if the execution will be external.
Supplier: Indicate the supplier when applicable.
The separation of Triggers by Time and Predefined Days corresponds to the updated model of the Programs template.
Frequency Activator
Use the Frequency Trigger sheet when execution depends on an accumulated reading, such as kilometers, operating hours, or cycles.
Name: Program Name.
Asset: Asset Name.
Component: Component Name, where applicable.
Task: Task Name.
Meter: Name of the meter associated with the asset. The meter must have been created beforehand.
Repeat every: Number of frequency units between executions. May contain decimal values.
Base frequency: Value used as an initial reference to calculate the next execution.
Frequency until: Value until which the detail will be valid, when applicable.
Is it external?: Indicate if the execution will be external.
Supplier: Indicate the supplier when applicable.
When migrating Preventive Maintenance by Frequency from Consuman, keep in mind that Evolution uses a base reading to continue calculating the next executions.
Time and Frequency Activator
Use the Time and Frequency Activator sheet when execution may depend on both elapsed time and a frequency of use.
Name: Program Name.
Asset: Asset Name.
Component: Component Name, where applicable.
Task: Task Name.
Repeat every (Time): Amount of time between executions.
Unit of Time: Use Day, Month or Year.
Base date: Date used as a reference for Time calculation.
Date to: Deadline, where applicable.
Meter: Name of the meter associated with the asset.
Repeat every (Frequency): Amount of frequency between executions.
Base frequency: Initial value used for frequency calculation.
Frequency up to: Limit value, where applicable.
Is it external?: Indicate if the execution will be external.
Supplier: Indicate the supplier when applicable.
Dual Frequency Activator
Use the Dual Frequency Activator sheet when the detail needs to consider two meters.
Name: Program Name.
Asset: Asset Name.
Component: Component Name, where applicable.
Task: Task Name.
Meter 1: First meter used for planning.
Repeat every 1: Quantity corresponding to the first Frequency.
Base frequency 1: Base value corresponding to the first frequency.
Frequency up to 1: Limit value corresponding to the first Frequency.
Meter 2: Second meter used for planning.
Repeat every 2: Amount corresponding to the second frequency.
Base frequency 2: Base value corresponding to the second frequency.
Frequency up to 2: Limit value corresponding to the second frequency.
Is it external?: Indicate if the execution will be external.
Supplier: Indicate the supplier when applicable.
Both meters must be associated with the reported asset.
Event trigger
Use the Event Trigger sheet when the execution of the Task depends on the fulfillment of a condition.
Name: Program Name.
Asset: Asset Name.
Component: Component Name, where applicable.
Task: The task that you want to schedule when the Event occurs.
Event trigger type: Indicate Measurement, Failure, or Response.
Meter (Per Measurement): For Measurement Events, indicate the Meter that should be evaluated.
Condition (By Measurement): Indicate the condition that must be met: Less than, Less than or equal to, Equal to, Greater than or equal to or Greater than.
Value (Per Measurement): Indicate the value against which the measurement will be evaluated.
Faults (By Faults): For Fault Events, indicate the Fault or Faults that will trigger the Event. If more than one is reported, separate them with a semicolon (; ).
Responses (Per Response): For events by response, indicate the response or responses that will trigger the event. If more than one is reported, separate them with a semicolon (; ).
Task (Per Response): For Events Per Response, indicate the Task whose Response should be evaluated.
Is it external?: Indicate whether the generated execution will be external.
Supplier: Indicate the supplier when applicable.
If the Trigger Type is Measurement, Meter, Condition, and Value must be completed. If it is Fault, Faults must be completed. If it is Response, Responses and Task must be completed.
Figure 7 – Example of a Programs file
[INSERT IMAGE]
Include a screenshot of Programs.xlsx showing the Programs sheet and some of the sheets corresponding to the different types of activators.
4.2.2. Measurements > Readings
Use the Readings.xlsx template to import the Reading history of the Assets.
Before performing the import, the Meters must be created manually and associated with the corresponding Assets.
Asset: Indicate the exact name of the asset to which the reading corresponds.
Meter: Indicate the exact name of the meter associated with the asset.
Date: Indicate the date and time the reading was recorded. Use the predefined format in the template, for example 8/30/2026 1:00:00.
Value: Indicate the value recorded for the Reading.
Reset: Indicate Yes when the reading corresponds to a reset of the counter.
Notes: Free text to incorporate supplementary information from the Reading.
When migrating Frequency Programs from Consuman, import the necessary history to maintain the reference used for planning. The migration document states that readings must be uploaded after the meters are created.
Figure 8 – Example of the Readings file
[INSERT IMAGE]
Include a screenshot of Readings.xlsx with examples of Active, Meter, Date, Value and a Reset case.
4.3. Configurations
4.3.1. Users > Users
Use the Users.xlsx template to import the Consuman Evolution Users.
In Evolution, the Email is the data used to uniquely identify the User.
Password: User identifier code. This is optional.
Names: Name or names of the person.
Surname(s): Surname(s) of the person.
Email: User's email address. It is used as a unique identifier and for system access.
Supplier: Enter the Supplier Name when the User is associated with one. This field is primarily used for Users with a Supplier License.
License: Specify the license you wish to assign to the user.
Roles: Specify the user role(s) to be assigned. Roles must already exist. When the field accepts more than one value, separate them with a semicolon ( ; ).
Location: Indicate the Name of the Location used to restrict User viewing, where applicable.
Primary Phone: User's primary phone number.
Secondary Phone Number: Alternative phone number.
Date of Birth: User's date of birth. Use the predefined format in the template.
Cost Per Hour: Economic value per hour corresponding to the User.
Specialty: Indicate the User's Specialty. The parameter must already exist.
Accounting Account: Specify the associated Accounting Account. If completed, the parameter must already exist.
Work Team: Indicate the Work Team to which the User belongs. It must have been previously created.
Additional User Data
Use the Additional-Data users.xlsx template to complete the Additional Data for Users already created.
Entity: For this file, complete with User.
Name: Enter the exact email address of the user to whom you wish to assign the additional information. For users, the email address is used as a unique identifier.
Dynamic field: Indicate the exact name of the additional data previously configured for users.
Value: Complete when the Additional Data is of type Text, Number, Drop-down list, or Multiple choice. If it allows multiple values, separate them with a semicolon (; ).
Check: Complete only when the Additional Data is of type Check. The template accepts TRUE and FALSE values.
Date: Complete only when the Additional Data is of type Date and Time. Use the predefined format in the template.
If the user already has a value entered for the same Additional Data, the new import replaces the existing value. The import does not create new dynamic fields.
Figure 9 – Example of the Users file
[INSERT IMAGE]
Include a screenshot of Users.xlsx showing the columns Names, Surnames, Email, License, Roles, Location, and Work Team.
4.3.2. Parameters > Parameters
Use the Parameters.xlsx template to import the parameters used in the different entities of Consumer Evolution.
Although this option is located at the end of this section to respect the order of the system modules, it is recommended to import the Parameters first, as they must exist before being used in the rest of the templates.
Name: Name that identifies the Parameter.
Type (Permanent): Select the Permanent Parameter Type to which the record belongs. The template includes a sheet with the available Permanent Types.
These include:
- Category.
- Subcategory.
- Unit of measurement.
- Purchase unit.
- Unit of measurement.
- Criticality.
- Specialty.
- Accounting account.
- Cost center.
- Urgency.
- Type of Job Application.
- Type of conformity.
- Program type.
- Supplier type.
- Type of equipment.
- Location type.
- Component type.
- Answer.
- Failure.
- Reason for stopping.
Type (Custom): Enter the name of a custom parameter type previously created from Settings > Parameters > Parameter Types . Use this column when the parameter does not correspond to one of the permanent types.
Do not simultaneously complete Type (Permanent) and Type (Custom) for the same record.
Conversion: Complete when the Parameter Type uses a conversion value. Enter the corresponding value according to the required configuration.
Abbreviation: Indicate the abbreviation used to represent the Parameter when applicable, for example in Units of measurement or Measurement Units.
Condition: Complete when the Parameter Type requires an additional condition associated with the value.
Asset Type: Complete when the Parameter configuration must be related to a specific Asset Type.
Priority order: Indicate the corresponding order using a numerical value when the Parameter Type uses a priority criterion, as in the case of Criticality.
Parameters that will be used later in Assets, Components, Tasks, Inputs, Vendors, or other entities must be created before importing those entities. Other imports do not automatically create new parameters.
Figure 10 – Example of the Parameters file
[INSERT IMAGE]
Include a screenshot of Parameters.xlsx showing examples of a permanent parameter and a custom parameter, highlighting the Name, Type (Permanent) and Type (Custom) columns.