Narrow source rollout
Start with one inbox, one folder, one drive location, one calendar feed, or one site section instead of a broad ingest.
Product
Capture from email, files, and websites
Polytrace gives teams a reliable way to capture inboxes, shared drives, calendar feeds, mailbox archives, and monitored sites. Teams can define what gets collected up front, stage archive imports for review, preview website scope changes before applying them, and keep a clear source trail from first receipt through the final record.
Highlights
Core capabilities
Archive batch staging
Upload mbox, PST, or zipped maildir as reviewable import batches before historical import starts.
Website scope preview
Preview crawl impact before broadening coverage so new pages do not enter the workflow unnoticed.
Clear source trail
Keep source context, version history, and auditability from receipt through later use.
Workflow
How this works in practice
Connect the source
Choose the inbox, mailbox, archive batch, drive location, calendar feed, or site section that owns the workflow.
Set the source scope
Define what is included, what is excluded, and how new data should enter over time.
Capture records with clear history
Receive or fetch source material, standardize it, and keep a clear record of what came in and when.
Review source-specific controls
Validate archive batches, preview crawl impact, and confirm boundaries before broadening coverage.
Activate downstream workflows
Use the captured records for search, extraction, monitoring, and controlled sharing.
Comparison
How Polytrace handles capture sources
| Source type | What teams usually need | How Polytrace supports it |
|---|---|---|
| Hosted inbox | Fast operational intake with the raw message preserved | Receives incoming mail into the right source and keeps the message context available for follow-up |
| Live mailbox | Ongoing sync from Gmail, Outlook, or IMAP | Uses clear source filters, tracks sync progress, and keeps history instead of overwriting older versions |
| Archive import | Historical mailbox recovery or knowledge retention | Stages original archive files as reviewable batches before starting a historical import |
| Drive source | Shared files and documents tied to the workflow | Connects specific file locations without forcing a whole-drive import |
| Calendar feed | Schedule-aware records that belong in the same operating layer | Captures calendar data alongside other sources so date-driven work stays connected |
| Website source | Controlled monitoring of site or portal pages | Uses preview and apply controls before crawl scope expands |
01
Start with clear source boundaries
Strong capture rollouts begin with one owned workflow and the exact sources that support it: a hosted inbox, a Gmail or Outlook account, a staged mailbox export, a SharePoint / OneDrive for Business library, a storage bucket, a calendar feed, or a monitored site section.
Polytrace makes that scope explicit through the source setup, connection, filters, and sync history. Teams can define what is in scope, what is excluded, and how new data enters the workflow before capture begins.
02
Handle live inboxes, archive uploads, and websites the right way
Hosted inbox capture is built for operational intake. Incoming mail is tied to the right source and preserved with raw message context so teams can work from the message itself instead of a thin summary.
Historical mailbox import runs as a staged batch process. Teams can upload original archive files such as mbox, PST, or zipped maildir, validate what was found, and then start a historical import from that checkpoint.
Website capture has its own review point. Scope changes go through a preview and apply flow so teams can understand the impact of expanding a crawl before new pages enter the workflow.
03
Keep the source trail and version history intact
Polytrace keeps new versions as they arrive instead of rewriting a hidden working copy. Teams can trace where a record came from, which version was current at the time, and what changed later.
The capture layer also helps prevent duplicate work with duplicate-prevention and versioning rules. Retries, rescans, and parser upgrades do not need to create duplicate records or muddy the history.
04
Make captured records useful immediately
Once records are captured, the same source material can feed search, extraction, monitoring, and controlled sharing. Teams do not need one intake path for search and a separate path for downstream workflows.
Support for Gmail, SharePoint, or websites matters, but the bigger win is consistency. Polytrace turns those sources into one reliable working layer without stripping away the original evidence.
05
A strong first capture rollout
The best first deployment is usually narrow and operationally painful: a catch-all intake mailbox, a monitored site section, or a mailbox archive that nobody can search well today.
Start with one source set, define the inclusion boundary, confirm what should be preserved, and connect the output to the next step. Once the capture model is trusted, expansion gets much easier.
Where this fits
Common starting points
- Catch-all intake inboxes that need controlled routing
- Historical mailbox uploads for continuity and searchability
- Site and portal capture where scope changes need review
- Shared-drive and calendar sources that support the same workflow
Related pages
Go deeper from here
Use the closest product, workflow, or security page to continue the evaluation.
Search and organize records
Polytrace helps teams search the full record across live and imported sources without losing original context.
Open pageMailbox knowledge retention
Use Polytrace for mailbox knowledge retention.
Open pageSite and portal monitoring
Use Polytrace for site and portal monitoring.
Open pageFAQ
Common questions
What sources does this support?
Polytrace works across Gmail, Outlook, IMAP, hosted inboxes, mailbox export files, Google Drive, SharePoint / OneDrive for Business, Blob Storage, calendar feeds, and websites. Exact rollout scope depends on the workflow, permissions, and how much of the source record the team needs to keep available.
Do teams need to capture everything at once?
No. Strong rollouts usually start narrow. Teams can begin with one inbox, one archive batch, one drive area, one calendar feed, or one monitored site section, then expand once the workflow and controls are working.
How do archive uploads work?
Archive imports are staged as reviewable batches. Teams upload original archive files, validate what the system discovered, and then start a normal historical import from that checkpoint.
How are website scope changes controlled?
Website source edits can go through a preview and apply workflow so teams can assess the impact of a scope change before it begins collecting additional pages. That keeps crawler expansion explicit and auditable.
Does Polytrace preserve the original source context?
Yes. Polytrace keeps the link back to the source record and version so teams can search, extract, monitor, and share from a trustworthy record of what actually came in.
Next step
See source capture in a live workflow
A strong demo starts with one real source set, one clear scope, and one output the team needs to trust.