Import and export

A new Customer arrives with records somewhere else. An App brings them in through a previewed Mapping, and hands every record back in one call, at any time.

Bring records inCopy Anchor Link

Riverside Property arrives with 140 leases in a spreadsheet. The import maps each column onto a Lease field and runs in test first:

1. The manager uploads the file, and the App proposes a Mapping: Unit to unit, End date to endsOn, Rent to rent.
2. The test run reports every row that fails, such as an end date with no year.
3. The manager fixes the rows and runs it live. The rows land in one Change, and the Tenant's renewals start.

A rerun of the same file writes nothing new. Leases that arrive this way are ordinary records, with their own history from the import on.

From another toolCopy Anchor Link

When the records live in another product, an Integration at the Customer's scope reads them through that product's API. The same Mapping and test run apply. The Customer approves the connection, and can revoke it at any time.

Take everything outCopy Anchor Link

Collection.export writes a Collection's records to a file, once or on a schedule. A Tenant's owner exports every record of the Tenant as JSON and CSV in one call, with no request to Leaseline.

An export is an Action like any other, so it appears in the audit log. A Customer that leaves keeps its data; nothing is purged.

NextCopy Anchor Link

Connected tools covers connecting a Customer's other tools for good.