Insights
Systems and records
92 guides · page 1 of 2
AI agent governance: access scopes, approvals and audit logs
AI agent governance for business systems: a per-system control sheet for agent scopes, approval triggers, audit log fields, retention and exclusions.
What data governance tools can and cannot prove in AI licensing
What data governance tools can export as evidence in an AI data licensing review, an evidence-to-tool matrix, the gaps no tool closes, and vendor questions.
Jira export 1000 limit: exporting a full project past the row cap
Jira export 1000 limit explained: slice the project with JQL, page the REST API for changelogs and comments, and prove completeness with a manifest.
Salesforce Data Loader export: a step-by-step guide with a manifest
Salesforce Data Loader export guide: settings, Export vs Export All, SOQL slicing, which objects to include, plus a manifest and completeness checklist.
Exporting Salesforce Knowledge articles: versions, languages, links
Salesforce export of knowledge articles, done right: which versions, languages and data categories to pull, how to query Knowledge__kav, plus a checklist.
Salesforce export object metadata for a data dictionary
How to export Salesforce object metadata for a data dictionary: describe and sf CLI routes, picklists by record type, validation rules, and what to leave out.
After an acquisition: archive or migrate the acquired company's systems?
Acquired company systems consolidation, system by system: decision rules for CRM, helpdesk, ERP and code, with an archive-first default that protects history.
Aggregated and usage data clauses: what vendors can do with your data
Aggregated data clause in a SaaS contract? Five common clause patterns, what each lets a vendor do with your records, and the fallback to ask for.
API rate limits and full-history exports: how long a large pull takes
API rate limits decide how long a large data export takes. Use a simple formula, see why child records multiply calls, and learn when bulk beats REST.
Archiving old Salesforce records to cut storage without losing history
Salesforce data archiving compared: delete, archive inside Salesforce or move records off-platform, and what each choice does to history and later access.
BIM 360 to Autodesk Construction Cloud: what happens to old project data
BIM 360 to Autodesk Construction Cloud migration for design firms: what to move, what to archive, and how to keep version history, RFIs and issues readable.
Bluebeam Studio Sessions and Projects: how long markups are kept
Bluebeam Studio session retention: why Sessions are temporary, how Projects differ, and how to export markup summaries before review history is lost.
CMMS work order history: keeping it when you switch systems
CMMS data migration guide: map assets, work orders, failure codes and parts history, and export them from Fiix, UpKeep, MaintainX or Limble before switching.
Company records in personal accounts and unpaid tools: who owns them?
Company data in personal accounts and free tools: why ownership and control differ, where shadow records hide, a risk matrix and a plan to consolidate them.
CRM migration checklist: history that doesn't move by default
A CRM migration checklist for the history imports drop by default: original dates and owners, stage history, email threads, files and closed-lost reasons.
Data retention vs minimization: keeping history without excess personal data
Data retention vs data minimization: keep the business event, reduce the personal detail. A record-by-record table, techniques and tool settings to check.
Deltek Vision to Vantagepoint: what project history to migrate
Deltek Vision to Vantagepoint migration, module by module: which project, time, billing, proposal and CRM history to carry, and what to archive.
Do helpdesk exports include internal notes and audit events?
Whether a helpdesk export keeps internal notes and audit events depends on the method. Compare CSV, full exports and APIs for Zendesk, Freshdesk and Intercom.
Do your software vendors train AI on your data? How to check
Do SaaS vendors train AI on customer data? Use a five-question checklist and see where AI terms live for help desk, CRM, chat, docs and meeting tools.
Downgrading SaaS plans to cut costs: what history you lose
SaaS downgrade data loss is easy to miss: lower tiers can hide old messages, stop audit logs and drop backups. See what changes and what to export first.
Dynamics GP end of life: what to do with decades of GP history
Dynamics GP end of life forces a choice: migrate open items, archive detailed history or keep GP read-only. Compare the options before support ends.
Epicor Prophet 21: archiving old orders before an upgrade
Prophet 21 data archive plan for distributors: when to purge or archive old orders before an upgrade, what to export first, and how to verify the export.
Epicor Vantage and Vista to Kinetic: what history to bring and what to archive
Epicor Vantage to Kinetic migration history, record by record: which jobs, quotes, NCRs and part revisions to bring forward and which to archive.
ERP migration: convert historical transactions or archive them?
ERP migration historical data, decided: convert open items and balances, archive full history in a queryable form, and keep the map of old IDs to new.
Exchange Server 2016 and 2019 end of support: archiving old mailboxes
Exchange 2016 and 2019 end of support leaves three paths: upgrade, move to the cloud, or archive and retire. See which mailbox history to save first.
Exit prep: documenting your systems and data history for buyers
Exit preparation data room template for systems: a register, a history map, export proof and data rights, so buyers trust your records before diligence.
Exporting job history from Workiz, Service Fusion or Successware
A field service software export checklist for Workiz, Service Fusion or Successware: job records to pull, filter traps and checks before you cancel.
Exporting Salesforce case history with feeds, emails and comments
Salesforce case history exports span Case, CaseComment, EmailMessage, FeedItem and CaseHistory. See the keys that rejoin them and what careless exports lose.
Franchise software: does the franchisor or franchisee own the job records?
Franchise data ownership for job records: a clause map across the franchise agreement, system software terms and post-term covenants, and who controls access.
Gong retention policies: how long calls are kept and who decides
Gong data retention policy explained: the default window, the library setting admins control, deletion after you leave, and why to export calls first.
How far back does Salesforce field history go?
Salesforce field history retention depends on standard tracking or Field Audit Trail. See how far back each goes, what it records and how to keep more.
How long do EDI providers keep your 850, 856 and 810 history?
EDI transaction history retention follows your provider's plan and contract, not your needs. Here is why to keep raw X12 and translated records yourself.
How long does ServiceTitan keep call recordings?
ServiceTitan call recording retention depends on your phone setup and agreement. Where recordings live, how to download them, and the consent checks to run.
How long does Zendesk keep closed tickets?
Zendesk ticket retention explained: when closed tickets are archived, when deletion schedules remove them, and how to check your account before history goes.
How long should a company keep customer support tickets?
Support ticket retention period by ticket type: the contract, warranty, dispute and privacy factors that set it, plus help desk settings that delete tickets.
How long should architects and engineers keep project records?
Architect record retention period explained by record type: the clocks that set it, which copy to keep from Deltek, Procore or Revit, and when files can go.
How many days do you get to export data after a SaaS contract ends?
There is no standard SaaS post-termination data export period. See which clauses set your window, what they leave out, and when to export instead.
How to archive Intercom conversations before switching tools
Archive Intercom conversations before you switch: what report exports and the API each give you, a step-by-step export, and formats that stay readable.
HubSpot inactive accounts: how a dormant portal loses its data
HubSpot inactive account deactivation for inherited or closed-company portals: how dormant data is lost, who can still log in, and what to export first.
Inactive mailboxes in Microsoft 365: keeping departed employees' email
A Microsoft 365 inactive mailbox keeps a departed employee's email searchable without an active user. Apply the hold first; here is the order and what stays.
Infor SyteLine history: what to archive when upgrading to CloudSuite
Planning a SyteLine to CloudSuite Industrial migration? See which job, routing, quality and order history to archive before cutover and how to keep it usable.
IT due diligence: system inventory and data history checklist for acquisitions
An IT due diligence checklist that adds what most skip: history depth, export paths, contract terms and data rights for every system the target runs.
Jira issue history: what full exports keep and lose
Jira export issue history guide: what CSV exports, site backups and the REST API keep or drop, from changelogs and worklogs to links and attachments.
Kantata project history: exporting before you switch PSA tools
Kantata data export for consulting firms: a record map of projects, resourcing, time, budgets and status reports, plus export paths to plan before a switch.
Keeping a legacy ERP read-only after go-live: costs, risks and alternatives
Legacy ERP read-only access feels safe after go-live but keeps costing. Compare read-only, archive platforms and database exports on cost, access and risk.
Leaving Bullhorn: exporting placements, notes and submittals
A Bullhorn data export guide for staffing owners: map placements, submittals and notes, pick an export route, and handle candidate data with care.
Leaving ServiceTitan: how to keep your full job history
Leaving ServiceTitan? A record-by-record export plan for jobs, estimates, invoices, equipment, memberships and calls, finished before your contract ends.
Legacy application decommissioning: archiving data before you retire a system
Application decommissioning data archiving in seven steps: the history to capture, the evidence to keep, and when to check retired records for licensing value.