# Historical transactions import

Want to see how you’re tracking against goal from your very first month? Share your historical transaction data with Flip.to and we’ll load it into Spacetime—so room nights and revenue are measured against your targets from day one, no waiting for new bookings to accumulate.

{% hint style="info" %}
**Before you begin:** This one’s for the data or IT contact at your property—whoever can pull a transaction export from your booking engine, PMS, or data warehouse. Your Customer Success Manager will help coordinate the hand-off, and is standing by if you have any questions along the way.
{% endhint %}

### What to include

Send every transaction with a **stay date** that falls inside the import window you’ve agreed with your Customer Success Manager. Stay date is the period the guest was physically on-property—so we need both **arrival** and **departure** dates to land each stay in the right goal months. Include the **reservation date** too, which is the date the booking was originally created.

### Required fields

A simple CSV works great. Use the field names below—they let us map your data straight into Spacetime.

| Field              | Description                                      | Format                                             |
| ------------------ | ------------------------------------------------ | -------------------------------------------------- |
| `name`             | Full name of the property.                       | String                                             |
| `code`             | Internal identifier used by the booking engine.  | Alphanumeric                                       |
| `reservation_date` | When the reservation was created, in UTC.        | `yyyy-MM-ddTHH:mm:ss` (e.g. `2026-03-15T13:25:21`) |
| `crs_number`       | Booking engine confirmation number.              | String                                             |
| `amount`           | Total pre-tax amount for the room purchase.      | Decimal (`0.00`)                                   |
| `currency`         | ISO 4217 3-character currency code (e.g. `USD`). | String                                             |
| `arrival_date`     | Check-in date.                                   | `yyyy-MM-dd`                                       |
| `departure_date`   | Check-out date.                                  | `yyyy-MM-dd`                                       |
| `adults`           | Total adult guests on the reservation.           | Integer                                            |
| `children`         | Total child guests on the reservation.           | Integer                                            |
| `rooms`            | Total rooms on the reservation.                  | Integer                                            |

### A few formatting notes

* **Dates** follow ISO 8601—`yyyy-MM-dd` for dates, and `yyyy-MM-ddTHH:mm:ss` in UTC for timestamps.
* **Amounts** are decimals, no currency symbols and no thousands separators.
* **Property codes** match what’s currently configured in your booking engine, so reservations line up with the right property in Spacetime.

### Sending it over

When the file’s ready, share it with your Customer Success Manager via a secure file share—Google Drive (link shared directly with your CSM), a one-time Dropbox link, or your own SFTP all work well. If you’d prefer a different method, just let your CSM know and we’ll set one up.

Once it’s loaded, hop back into the **Goals** tab and you’ll see history feeding into the same calendar heat map and progress views—ready to dial in from there.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flip.to/docs/platform/spacetime/goals/historical-transactions-import.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.