Yardi Voyager support

Last updated date:

Connect, reconnect, and troubleshoot Yardi Voyager without sharing credentials or customer content through support channels.

1. Before you start

  • Coordinate an approved Voyager export, Data Connect, Replicate, backup, or file-drop process through Yardi Client Central, the Interface Program, or the organization's Yardi account team.
  • Grant the extractor YARDI_BACKUP:Read and YARDI_SQL_EXPORTS:Read only for the approved account and artifact locations.
  • Provide the stable account ID plus either the artifact directory or both request and result directories; do not place unrelated exports or secrets in those paths.
  • Do not send Yardi Voyager credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Yardi Data ConnectYardi's Data Connect product information.

2. Connect Yardi Voyager

  1. In Seedling, open Connections and choose Yardi Voyager as a workspace administrator.
  2. Enter the stable Yardi account ID and optional account label.
  3. Provide either the approved artifact directory or both extractor request and result directories, plus an optional backup path.
  4. Connect and verify that Seedling discovers only the intended artifact set and projects the expected property and accounting records.
  5. Assign exact-connection data-type or property scopes to active members before expecting human reads.

3. Authorization and connection problems

Artifact path rejected
Provide one approved artifact directory or both extractor request and result directories. Paths must be configured for the Seedling runtime and must not be public or arbitrary workspace roots.
No extraction result
Confirm the Yardi-side job has read-only access, wrote the expected artifact to the configured directory, and used the verified account ID.
Member cannot read records
Assign the applicable exact-connection data-type or property scope. Workspace membership, administrator status, and stewardship alone do not grant raw access.

4. Missing or delayed data

  1. Confirm the record exists in the approved backup or SQL export and belongs to the verified Yardi account.
  2. Check extraction timing, file completeness, schema/version warnings, and configured artifact/request/result paths.
  3. Confirm the member has the matching record-type or property declared scope on this exact source.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Generate a fresh approved export or rotate the file-drop location according to the organization's Yardi extraction process.
  2. Update the exact Seedling connection with the new artifact or request/result paths and verify the same account ID.
  3. After Seedling confirms the new path, retire the old artifact location under the organization's retention and secret-handling policy.