Skip to main content
Move to the new Calendar
Search
Search Calendar Classic Support Help and Support.

This article applies to:

  • Product: ONESOURCE Calendar Classic

Phase 1: Preparation and data analysis

Back up your Calendar classic data

It's important to create a complete backup of your Calendar Classic environment before proceeding.
  1. Go to Events in Calendar Classic.
  2. Clear all search filters, then select
    Search
    .
  3. Select
    Export All
     to back up your files.
  4. Save the export file as a historical record.

Analyze and determine event scope

  1. Export current year events.
    1. Filter the Classic grid by current year due dates (or use the
      Year
       field).
  2. Select
    Actions
    Export All
    .
  3. Review this export to identify Year/Entity/Event Template combinations to move to the new Calendar.
  4. Identify current lists of entities and jurisdictions to set up or turn on.
  5. Determine which custom fields to keep or eliminate that are customer-defined or system generated.
  6. Determine if you are using Certified Mail, as additional information will be moved from Classic.
note
When you identify items to move to the new Calendar, remember to create your current year items. If entities have a calendar year end, then the current calendar should show 2024 Tax Returns/Extensions and 2025 Estimated Payments. You have already extracted prior year events in Step 1, and you can reference them from that file.

Map classic events to the new Calendar obligations

Download the Global Content Library (GCL)
  1. Go to the new
    Calendar
    Schedule Due Dates
    Export
    Export Content Library
    .
    1. This GCL provides a list of all obligations (also known as Event Templates) that the new Calendar supports.
Create your mapping
For each Year/Entity/Event Template combination you plan to move:
  1. Find the classic Event Template Name in Column X of the Global Content Library file.
  2. Select the Obligation or mark it as
    to be used
    .
    1. The list of Obligation IDs you select shows the list of jurisdictions and domains that you'll need to turn on in the next steps.
  3. In your Classic export file, record the matching Obligation Name and ID for each Year/Entity/Event Template combination.
    1. You'll use this obligation ID in the next steps when you create your new records.
How to handle multiple obligations
Some Classic Event Templates may correspond to multiple Obligation IDs. This occurs when obligations differ by entity type (for example, Corporation or Partnerships), effective dates, or filing methods like e-file versus paper.
Some new Calendar Obligation IDs map to multiple Classic Event Templates. For example, the U.S. 1120 used to have 2 Event Templates in Classic depending on the entity's year end. The new Calendar provides the correct deadline automatically.
Identify custom due dates
If no matching Obligation exists in the GCL, you'll need to create these as custom due dates.