Data Exports

Absorb provides powerful and flexible reporting capabilities directly in the admin portal. However, if the built-in reports do not meet your needs, a custom data export can be created (sometimes referred to as a "Custom Report"). These exports can be delivered by email or secure FTP, with data included to meet your specific business needs. In addition to custom admin reporting, this is also a great solution for automatically feeding data from Absorb into an external application (e.g. Salesforce, Workday, etc). If you want to request a custom data export, please contact your Client Success Manager.

It's important to note that these data exports are not on-demand reports and include no user interface (aside from whatever application you use to open, view and/or edit the export file itself).

Not what you're after? You may be interested in our full-service Absorb Analyze offering!

Special Considerations

Basic and Advanced Data Types

Basic exports contain one or more of these data types:

  • Users
  • Courses
  • Departments
  • Course Level Enrollments
  • Categories
  • Groups

Advanced exports are in exports involving at least one of these data types:

  • Question Banks
  • Answers
  • Assessments
  • Session Level Enrollments
  • Activity Enrollments

You can find more information in our Absorb Data Mapping article.


Date and Time Fields

This section outlines the functionalities of both the Pre-Defined and Custom Date and Time fields.

Pre-Defined Fields

  • Date Hired and Date Terminated
    • These are date format fields in the User object. Our export tool does not convert them to Portal Timezone but leaves them as UTC during the export. The LMS saves the value in UTC to the database and appends 00:00:00 as the time.
    • The export will obey the UTC time (i.e., not converting to the client’s Portal Timezone). For example, if the Date Hired is 2024/05/21, then the exported value is 2024/05/21 00:00:00 as the value stored in the database.

  • Other Object Fields
    • All other Date or Date and Time fields are stored in the database converting to UTC from the interface with their portals' timezone. When it comes to export, our export tool converts the Date and Time to align with their portals' timezone.
    • For example, if the Enrollment Completion Date is 2024/05/21 12:38:00 PM MT, the exported file would have the same value as what the clients see on the interface.

Custom Fields

  • Date Format
    • Since the LMS ignores the time, when it saves to the database, the time will be stored as 00:00:00. Our export tool would convert it to align with the client Portal Timezone.
    • For example, the client puts 2020/05/01 in their Portal for the Date Format custom field, the Portal timezone is Eastern.
      • When the Date falls in the winter time (no daylight savings), the exported value will be 2020/04/30 19:00:00.
      • When the Date falls in the summer time (i.e., during daylight savings), the exported value will be 2020/04/30 20:00:00.


Please note that the times in the above example are in EST.

  • Date & Time Format
    • In this case, the client would provide the exact time when saving to the database. The time will be converted to UTC and the export will convert it to the client Portal Timezone.
    • For example, if a client has 2020/05/01 08:00:00 in their Portal for the Date & Time custom field. The Portal Timezone is Eastern, the exported value will be what they see on the interface, 2020/05/01 08:00:00.

Export Process

Export Steps

We'll walk you through the following steps to scope and develop a custom data export:

  1. Pre-scoping: Your Client Success Manager will work with you to gather background and requirements. At this point, we're usually looking to confirm that a custom data export really is the best solution for you and if so, what you want the export to look like. Please provide a mock-up or sample of the desired export at this time. Our development team may do a preliminary investigation at this time if the request is particularly complex or non-standard.
  2. Requirements Document: Your Client Success Manager will work with you to fill out the Data Export Requirements Document. The completion and approval of this document allow the work to be added to our development queue.
  3. Analysis: Our development team will review the completed requirements document for completeness and clarity. Additional questions may be asked at this time.
  4. Development: A developer creates a sample report, usually from your production data in your Absorb portal. 
  5. Review: Your Client Success Manager will provide the sample and request feedback.
  6. Revision (Optional): Let your Client Success Manager know if any changes are required. A new sample will be provided after revisions are made.
  7. Approval: If everything looks good, provide your Client Success Manager with written approval to proceed to deployment.
  8. Scheduling & Deployment: Once approved, the report is set to run according to the requirements document's schedule. 
  9. Confirmation: We'll ask for final confirmation once the report is running in production and formally close out the request.

What Fields or Filters Are Included?

Most fields you can view in the LMS can be included in an export. In addition to the types of filters that you're used to adding through the Absorb admin interface like "Date Added is last month", more advanced filters like "Date Added is last month AND (Department = HR OR Employee Number contains ABC)" can usually be supported. Depending on the combination of fields, filters, and volume of data that will be included, sometimes we may suggest alternatives that are more efficient to generate. After reviewing your requirements, our development team will advise you if anything needs to be changed. Please review the "What's not supported?" section at the bottom.

Some types of data in Absorb cannot be included in exports, most notably audit history and rules, for example, course enrollment rules. 


Simple aggregation is generally supported. Choose the field(s) you would like to group records by and then the aggregate method for the other fields. For example, you might say, "Give me all enrollments for courses in the "Project Management" category, grouped by unique user, with the score displayed as an average across all applicable enrollments for that user." Not sure if you need this? Provide a sample and description of what you're looking for, and we can confirm during the scoping process.

Cumulative vs. Deltas

The majority of our data exports are generated as delta files. Delta files will only contain data that has changed since the last time a file was sent rather than sending a complete extract each time. This is usually accomplished by applying a date filter to the report, for example, by only including course enrollments with a Date Completed yesterday for a daily report. Full extracts are usually impossible because the file will grow too large, and the generation time will eventually be too long.


Email, FTP, or both can deliver exports. A distribution list controlled by the client is usually preferred for email delivery so that the individual recipients can easily be changed without our intervention. Files larger than 10MB cannot be emailed. More information about FTP delivery can be found in our FTP Support for Integrations article.


Exports can be scheduled to run daily, weekly, monthly, quarterly, or yearly. The specific time we start generating the export is usually very early in the morning (~1 - 5 am) North American Mountain Time, though different times can be requested. Schedules are dependent on the type and amount of data being generated and are subject to approval by Absorb.

File Format

Files are generated in CSV format, delimited by commas by default (other delimiters such as Semicolon (;) and Pipe/Bar (|) can be used upon request). Below are a few visual examples opened in a text editor and Microsoft Excel, though keep in mind that sometimes these exports are meant to simply be imported by another application and not read by a human:

Sample Enrollments Export:

- Text Editor:

- Excel:

Comments: In the example above, HRID could represent a number of things:

  • A custom column header for a column containing the user's External ID
  • A custom user field named HRID
  • A custom column header for a column containing some other user field (likely some kind of unique identifier)

Sample Courses Export:

- Text Editor:

- Excel:

What's Not Supported

There are some things a data export can't do, listed here in no particular order:

  • Data exports are always scheduled or one-time. There is no interface available for requesting the export on demand.
  • Data exports are plain text, formatted as character separated values, generally with a .csv or .txt extension. Other formats such as XML, PDF, etc. are not supported.
  • As a result of the above, text formatting, images, cell highlighting, etc. are not supported.
  • Advanced or custom calculations/formulas are not supported. Basic aggregate columns such as min, max, sum, average, etc. are generally supported (in SQL terms, this would be a "group by"). Feasibility will be scoped and confirmed by Absorb.
  • Typically, multiple aggregations such as a sum of one field and a count of another field are not possible. 
  • Conditional logic such as "if column A equals "ABC" then populate column B with value "XYZ"”. 
  • Dynamically generated columns such as "add one column for each course taken" - we will usually suggest a way of restructuring your report to avoid this. 
  • Dynamically generating multiple versions of a report for each admin user, with different data included for each user depending on their User Management settings.
Was this article helpful?
0 out of 2 found this helpful


1 comment
Date Votes
  • Be helpful if there was an example of how to actually request the data Export


Article is closed for comments.