How to Import Cards via CSV

Importing cards via CSV allows you to create or update multiple records at once, ensuring speed and standardization of information. **1st Step: Accessing the Cards Module** In the upper left side menu, click **“Cards”** to open the available list. You can navigate through the pipeline tabs at the top to choose which workflow you want to import cards into.

**2nd Step: Downloading the Import Template** 2. In the Cards list, click the **"Import CSV"** button represented by the upload icon in the upper right corner. 3. In the **“Import Data”** window, click **"Download Template"** to obtain the CSV model.

The template contains the required columns:       • **code** (card tracking code)       • **name** (card name)       • **tags** (associated tags, separated by commas)       • **sla** (configured deadline in hours)       • **last\_stage\_updated\_at** (date/time of the last stage movement)       • **pipeline** (pipeline name)       • **pipeline\_stage** (current stage name)       • **owner\_user** (name of the responsible user)       • **creator\_user** (user who created the card)       • **pipeline\_uuid** (unique pipeline identifier)       • **pipeline\_stage\_uuid** (unique stage identifier)       • **owner\_user\_uuid** (unique identifier of the owner)       • **creator\_user\_uuid** (unique identifier of the creator)       • **created\_at** (creation date and time)       • **updated\_at** (last edit date and time)       • **cf\_** (custom field columns, if applicable) **3rd Step: Filling Out the CSV File** 2. Open the template in a spreadsheet editor and fill each row with the card data. 3. Keep the exact column order. 4. Use UUIDs whenever possible to avoid ambiguity. 5. Save the file in **CSV format** without changing the header. **4th Step: Importing the Completed File** 2. In the **“Import Data”** window, drag the CSV file into the indicated area or click to select the file. 3. Click **“Import Data”** to start the import. **5th Step: Finalizing the Import** 2. After processing, the following message will appear: **Success! The cards were imported successfully.** 3. The Cards list will reload, showing the new records or updates. **Best Practices:** • Always use the official template to avoid errors. • Prefer UUIDs for pipelines, stages, and users. • Test with a small number of rows before importing large volumes. • Keep a backup of the original CSV file. • Validate **cf\_** columns (Custom Fields) when using custom fields. **Conclusion:** By following this process, you can import cards quickly and in an organized way, ensuring consistency in the information. If you have any questions, contact support.