Connection 01
Tenant-specific mapping
Review fields, statuses, products, prices, and business rules for the company being imported.
Migration and imports
Rivet’s import approach separates mapping, validation, preview, and application so existing rental businesses can move carefully instead of starting over.
What connects
Connection 01
Review fields, statuses, products, prices, and business rules for the company being imported.
Connection 02
Find missing values, duplicates, invalid references, and unsupported records before writing live data.
Connection 03
Workspace owners can use tenant export controls for supported company data.
How it works
Each stage preserves the customer, rental, tenant, and operating context needed by the next one.
Identify the spreadsheets, payment exports, customer lists, agreements, and operational records that matter.
Translate source fields into tenant-scoped customers, rentals, inventory, statuses, and supporting records.
Review counts, duplicates, missing relationships, and exceptions before applying the import.
Import the approved scope, compare totals, and retain a record of what moved and what requires manual follow-up.
Operational outcomes
01
The team understands what will change before the new system becomes the operating source.
02
Duplicates and incomplete records are handled as explicit exceptions.
03
Rivet adapts the import to the tenant instead of copying another company’s pricing or workflow blindly.
Questions
Not safely without review. Rivet supports structured validation and mapping, but each source must be assessed for its fields, quality, and business meaning.
Relevant payment history can be evaluated as part of a migration, but it must be reconciled to the correct tenant, customer, rental, and accounting treatment.
Supported agreement files and metadata can be mapped into the tenant’s document workflow when included in the approved migration scope.
Rivet includes tenant export controls for supported workspace records.
Keep exploring