Convert XLSX to YML

Why Convert XLSX to YML?

Converting XLSX to YML allows you to transform Excel spreadsheet data into the widely-used .yml file format favored by DevOps tools and modern application frameworks. Many tools specifically expect the .yml extension -- Docker Compose looks for docker-compose.yml, GitHub Actions reads .yml workflow files, and Ruby on Rails uses database.yml. Having your data in .yml format ensures direct compatibility with these ecosystems.

The .yml extension has become the de facto standard in many development communities. While technically identical to .yaml, the shorter .yml extension is preferred by tools like Docker, GitHub, GitLab CI, Travis CI, and CircleCI. Converting your Excel data to .yml format means the output files are immediately usable with these tools without renaming.

YML's human-readable syntax makes it ideal for configuration data that teams need to review and maintain. Unlike XLSX files that require Excel to inspect, YML files can be opened in any text editor and understood at a glance. The indentation-based structure clearly shows data relationships, making it easy to verify that converted spreadsheet data is correct.

Our converter reads the XLSX workbook, extracts data from the first sheet, and generates a properly formatted YML file with a sequence of mappings. Each row becomes a mapping entry with column headers as keys and cell values as properly typed YML values, ready for immediate use in your development workflow.

Key Benefits of Converting XLSX to YML:

• DevOps Compatible: Direct use with Docker Compose, GitHub Actions, and CI/CD pipelines
• Tool Standard: Many tools default to .yml extension for configuration files
• Human-Readable: Clean indentation-based syntax easily understood by developers
• Typed Values: Numbers, booleans, and strings are properly represented
• Version Control: Clean text diffs in Git for collaborative data management
• Framework Ready: Compatible with Rails, Spring Boot, and other .yml-consuming frameworks

Practical Examples

Example 1: Employee Directory

Input XLSX file (employees.xlsx):

Excel Spreadsheet - Sheet1:
+--------+-----------+-------------+--------+
| Name   | Title     | Department  | Ext    |
+--------+-----------+-------------+--------+
| Alice  | Engineer  | R&D         | 1201   |
| Bob    | Designer  | UX          | 1305   |
| Carol  | Manager   | Operations  | 1102   |
+--------+-----------+-------------+--------+

Output YML file (employees.yml):

- Name: Alice
  Title: Engineer
  Department: R&D
  Ext: 1201
- Name: Bob
  Title: Designer
  Department: UX
  Ext: 1305
- Name: Carol
  Title: Manager
  Department: Operations
  Ext: 1102

Example 2: Environment Configuration

Input XLSX file (environments.xlsx):

Excel Spreadsheet - Sheet1:
+-------------+-----------------+------+---------+
| Environment | Host            | Port | Debug   |
+-------------+-----------------+------+---------+
| development | localhost       | 8000 | true    |
| staging     | staging.app.com | 443  | false   |
| production  | app.com         | 443  | false   |
+-------------+-----------------+------+---------+

Output YML file (environments.yml):

- Environment: development
  Host: localhost
  Port: 8000
  Debug: true
- Environment: staging
  Host: staging.app.com
  Port: 443
  Debug: false
- Environment: production
  Host: app.com
  Port: 443
  Debug: false

Example 3: Server Inventory

Input XLSX file (servers.xlsx):

Excel Spreadsheet - Sheet1:
+----------+----------------+------+-------+-----------+
| Hostname | IP Address     | CPU  | RAM   | OS        |
+----------+----------------+------+-------+-----------+
| web-01   | 192.168.1.10   | 4    | 16 GB | Ubuntu 22 |
| db-01    | 192.168.1.20   | 8    | 64 GB | CentOS 9  |
| cache-01 | 192.168.1.30   | 2    | 8 GB  | Debian 12 |
+----------+----------------+------+-------+-----------+

Output YML file (servers.yml):

- Hostname: web-01
  IP Address: 192.168.1.10
  CPU: 4
  RAM: 16 GB
  OS: Ubuntu 22
- Hostname: db-01
  IP Address: 192.168.1.20
  CPU: 8
  RAM: 64 GB
  OS: CentOS 9
- Hostname: cache-01
  IP Address: 192.168.1.30
  CPU: 2
  RAM: 8 GB
  OS: Debian 12

Frequently Asked Questions (FAQ)

Q: What is the difference between YML and YAML?

A: YML (.yml) and YAML (.yaml) are the same format with different file extensions. The content, syntax, and specification are identical. The .yml extension originated from the DOS/Windows 8.3 filename convention that limited extensions to three characters. Many tools such as Docker Compose, GitHub Actions, and Travis CI use .yml by default, making it the more commonly seen extension in DevOps contexts.

Q: Which worksheet is converted from the XLSX file?

A: The converter processes the first (active) worksheet in the XLSX workbook. If your file contains multiple sheets, the data from the first sheet will be extracted and converted into YML. You can reorder sheets in Excel before conversion if you need a different sheet converted.

Q: How are data types handled in the conversion?

A: YML has native type inference. Numeric values from Excel become YML integers or floats, and text values become strings. Values that could be ambiguously typed (such as "yes", "no", "on", "off" which YML interprets as booleans) are quoted to preserve their intended string meaning when necessary.

Q: Are Excel formulas preserved in the YML output?

A: YML does not support formulas or computed values. The converter extracts the calculated results from formula cells and writes them as properly typed YML values. A cell with =SUM(A1:A5) evaluating to 150 will appear as 150 (an integer) in the YML output.

Q: Can I use the output directly with Docker Compose?

A: The generated YML is valid YAML that any parser can read. However, Docker Compose expects a specific schema (services, volumes, networks, etc.). The converted data represents your spreadsheet rows and would need to be restructured to match Docker Compose's expected format. The data can serve as a starting point for generating Docker configuration.

Q: Why is indentation important in YML files?

A: YML uses indentation with spaces (never tabs) to define data hierarchy. Two spaces per indentation level is the most common convention. Incorrect indentation causes parsing errors or misinterpreted data structure. The converter produces consistently indented output that follows standard YML formatting conventions.

Q: Is cell formatting preserved in the YML output?

A: No. YML is a data serialization format that stores only values and structure, not visual formatting. Bold, colors, borders, and font styles from Excel are discarded. Only the raw cell values are preserved as properly typed YML data.

Q: How does the converter handle large spreadsheets?

A: The converter processes spreadsheets of any reasonable size. Each spreadsheet row becomes a mapping in a YML sequence, so the output grows linearly with the number of rows. YML files remain parseable regardless of size, and the human-readable format makes it easy to inspect even large data files.