Import from a spreadsheet

You've probably been tracking this work somewhere already, often a Google Form that feeds a sheet. Bring it with you, so your history and reports start on day one.

Let us set it up (recommended)

1. On the Stacks page, click Import.
2. Drop in your file: Excel (.xlsx) or CSV. Every tab is read, so you don't need to tidy it first. Or paste a Google Sheets link (more below).
3. Our AI reads your column names and a few sample answers and suggests the new stack. You'll see:
   • The new stack: its name, ticket prefix and color. Click Choose an icon to give its colored square an icon, the same way as in the stack editor.
   • Tabs: which tabs hold the tickets. A form's open tab and a "Resolved" or "Completed" tab with the same columns come in together; tick Finished work on a tab and its rows arrive closed. Tabs that are something else, like audits or lists, are left out.
   • Columns: what each column is for. The request itself becomes the ticket's details and title, the Timestamp becomes the date it came in, a store column becomes a Location, and the rest become fields. Change anything with Used for, Field name and Type.
   • Stages: how tickets move, like New → Received → Resolved. Checkboxes such as "Request Received" or "Issue Resolved", a finish date or a finished tab decide where each row lands. Make the stages your own before you import: rename one, + Add a stage, remove one with ✕, or move it with the arrows. Tick Finished on the stages that close a ticket. Each stage shows how many tickets will land in it.
   • If a column is used for Status, you start with one stage for each status in the sheet. Under Where each status goes, pick the stage for each status, so "Waiting on parts" and "Ordered" can share one stage.
   • Locations: stores the sheet names that you don't have yet. Each is added as a new location unless you match it to one you have, or leave it blank.
   • Preview: how many tickets, how many open and finished, empty rows skipped, and anything that didn't fit its field.
4. Click the button at the bottom (it says Create, your stack's name and how many tickets). The stack and every ticket are made in one go.

Want to add rows to a stack you already have, or match every column yourself? Click Import step by step under the upload box.

From a Google Sheets link

Paste the sheet's link and click Open sheet. The sheet has to be shared as Anyone with the link can view (in Google Sheets: Share → General access). Got a Google Form? Open its Responses tab, click View in Sheets, and paste that sheet's link. Prefer not to share it? Use File → Download → Microsoft Excel and upload the file. The new stack is named after the sheet's title; change it on the next screen.

Made to be safe

• Imports send no emails and fire no triggers. Nobody gets 400 "We got your request!" messages.
• Tickets keep their original dates, including when finished ones were finished.
• Owners are matched to teammates by email, name or initials (so "TM" can be Taylor Morgan).
• Our AI sees only column names and a few sample answers, never your whole sheet, and nothing is saved until you click import.
• Changed your mind? Go to Settings, then Imports, and click Undo import within 30 days. It deletes exactly the tickets that import made; if the import made the stack, Delete the tickets and the stack removes that too. Locations it added stay.

Match names to people later

People who weren't in TicketStacker yet when you imported come in as plain names, like "Justin" in an Assigned To column. Once they've joined, go to Settings → Imports and click Match names to people on that import. For each column of names, pick who each name is (we guess from names and emails), then click Match. Open tickets get that person as the owner, unless they already have one, and finished tickets show them as Closed by. Shared names like "Justin or Patrick" are left alone: put those tickets in a queue for the two of them.

Only company Admins can import.

Walkthrough: Move from Google Sheets in an afternoon.