Importing Measures

Two Import Data Type options load measures from an Excel spreadsheet. Measures creates measures, and updates measures that already exist. Measure Values (Time Phased) loads values onto measures that already exist, such as their plan, actuals and forecast. You set up either one from an initiative's Tools > Integrations page, by clicking New Integration, leaving the Adapter as Excel, and selecting the Import Data Type. Load the measures first, then their values.

This article covers the Advanced Model only. Neither import type is offered on a Simple Model program. Both need the Integrations permission on the initiative, as set out in Before you start. For what measures are, see Managing Measures.

This is different from Administration > Integrations, which connects third-party applications. See Connecting a Third-Party Application.

Before you start

Who can import

Importing needs both of the following:

• Enable Integrations turned on for the initiative. It is a setting on the initiative's classification, under General Configuration. See Configuring Initiative Classifications (Advanced Model).
• The Integrations permission set to Full on a team role held on the initiative. See Team Roles. A Full Admin, or a user whose admin role sets Hierarchy to Full, can import without a team role. See Admin Roles.

Where either is missing, Integrations isn't offered under Tools.

What must exist first

These imports don't create anything other than measures and their values. Set up the following before importing:

• Measure classifications — each measure's classification must exist and be active. It must also be selected under Allowed Measure Classifications on the classification of the initiative the measure sits under. See Configuring Measure Classifications (Advanced Model).
• Owners — each owner must be an existing, unlocked user, and not a guest user.
• Units — each unit must exist and be active. See Measurement Units.
• Initiatives to sit under — every initiative a measure sits under must already exist. See Importing Initiatives.
• Custom fields — a custom field must be mapped to the measure classification to be filled in, and any option a cell names must exist. See Custom Fields (Advanced Model).
• Measures — for Measure Values (Time Phased), every measure in the file must already exist. Create them in Amplify, or import them first with Measures.

Where to set up the integration

Set the integration up on the highest initiative that holds every measure in the file. A measure can be created, or have values loaded, only at or below the initiative the integration is set up on. A row for anything outside it fails.

Enterprise measures, which are labeled Shared, sit at the top level of your hierarchy. To create them, or to load values onto them, set the integration up on the top-level initiative. That needs a Full Admin, or an admin role with Hierarchy set to Full. Updating measures is different: see Updating measures later.

File limits

• The file is an Excel file (.xlsx) of 5 MB or less.
• The sheet has up to 2,000 rows. The row of column headings isn't counted where Header? is selected. A sheet with more can't be run, so split it into several sheets or files.
• Only one sheet is read each time the integration runs. The sheet is chosen when the file is uploaded.

Preparing a measures spreadsheet

Put one measure on each row, with a column for each field. A row of column headings at the top makes mapping easier. The columns can be in any order, but each integration remembers the mapping by column position, so keep the order the same from one run to the next.

Columns to create measures

A created measure needs all of the following:

• Parent Initiative — the initiative the measure belongs to. It can be matched on its name, Amplify ID or External ID. It must be the initiative the integration is set up on, or one beneath it. It can't be a program: a row that names one fails, with a message that the program's classification "doesn't support standalone Initiative level Measures".
• Classification — matched on the classification's name or ID. It must be allowed on the classification of the initiative named in Parent Initiative. Where it isn't, the row fails with the message "Classification not allowed through parent initiative".
• Owner — matched on the user's name, email or ID.
• Name — a name longer than 120 characters is shortened.
• Start Date and End Date — see Dates and reporting cadence.
• Unit — matched on the unit's name or ID.
• Reporting Cadence — how often a value is recorded. Enter MONTH, QUARTER or FINANCIAL_YEAR, in capital letters. Any other text fails the row.

Where the classification has required custom fields, include a column for each. A row that leaves one blank isn't created.

A created measure takes its other settings from its classification: whether it is an advanced measure, its plan settings, whether actuals are recorded, and its forecast. To load plan values that differ from those settings, use Measure Values (Time Phased) once the measures exist.

Initiative and enterprise measures

The Parent Initiative decides which kind of measure a row creates:

• Initiative measure — the row names an initiative. The measure belongs to that initiative, and can be used only by benefits under it.
• Enterprise measure — the row names the top-level initiative of your hierarchy. The measure is created as an enterprise measure, labeled Shared, which any benefit can use. The integration needs to be set up on the top-level initiative, and the measure's classification needs to be allowed on the enterprise's classification too.

Columns to update measures

To update measures that already exist, include one column that identifies each measure: its ID or its External ID. The other columns hold the fields to change. See Updating measures later.

Optional columns

• External ID — a reference from another system. It must be unique across measures, and it can be used later to find the measure again. It is set only through the Identifier Lookup column. Turn on Enable External ID on the measure classification to show the field on its measures.
• Description — chosen from the Attribute list.
• Custom fields — one column for each custom field mapped to the classification.

Dates and reporting cadence

Enter dates in a format that gives the year, month and day unambiguously, such as 2026-01-01. A cell that isn't a date shows a red icon. A created measure has to start and end on whole periods of its Reporting Cadence:

• Start Date — the first day of a month.
• End Date — the last day of a month, later than the start date.
• MONTH — any month can start or end the measure.
• QUARTER — the measure starts in the first month of a quarter, and ends in the last month of a quarter.
• FINANCIAL_YEAR — the measure starts in the first month of the financial year, and ends in its last month.

Quarters and financial years follow the instance's financial year end. For example, where the financial year ends on 30 June, a quarterly measure starts on 1 July, 1 October, 1 January or 1 April, and a financial year measure starts on 1 July and ends on 30 June. A start date that isn't the first day of a month, or an end date that isn't the last day of a month, fails with the message "Not a valid date". A date that doesn't suit the cadence fails with the message "The date does not match what is allowed via the Classification and Financial Year".

Where the measure classification locks a setting, such as the Unit, the locked value is used in place of the cell, and the cell shows an amber warning.

These rules apply to created measures. On an update, a start date is moved to the first day of its month and an end date to the last day of its month.

Preparing a measure values spreadsheet

Use one row for each value, not one column for each month. A measure with a Plan of 1,000 in January and 1,500 in February takes two rows: the measure, Plan, January, 1,000; and the measure, Plan, February, 1,500. A measure with both Plan and Actual values takes a row for every period of each series.

To load values onto the measures that benefits use, you can also use Benefit Values (Time Phased) with Parent Type Measure. See Importing Benefit Values. That route finds a measure by name or ID only, not by External ID. Where your instance calls benefits Impacts, these labels read Impacts instead.

Columns for measure values

The spreadsheet needs these four columns. The column headings can be anything, because each column is mapped by its position. The names below are the ones you map the columns to.

• Parent — the measure the value belongs to, identified by its name, its ID, or its External ID. Matching on name uses the first active measure with that name, so use the ID or External ID where two measures share a name.
• Series — which series the value goes in. See Choosing the series.
• Start Date — the first day of the period the value is for.
• Value — the amount.

Any other column, such as a column of measure names, is mapped to No Action.

A measure is found only where it sits on an initiative at or below the integration's initiative. An enterprise measure is found only where the integration is set up on the top-level initiative. A measure that was created automatically with a benefit isn't found: use Benefit Values (Time Phased) for those. A row for a measure that isn't found is skipped, with a message that the measure does not belong to this hierarchy.

Choosing the series

The names are not case-sensitive. Use the series names as your instance shows them. The series a measure accepts depend on its classification:

• A measure whose classification has Advanced Measure turned on — CMO, FMO, Actual, or Forecast. CMO and FMO are the measure's two plan series. See Configuring Measure Classifications (Advanced Model).
• Any other measure — Plan, Actual, or Forecast. A Plan value is saved as the measure's plan.

A row with any other series for the measure is skipped.

Rows that are skipped

A row is skipped, and the rest of the file still imports, where:

• The series is Forecast and the measure's classification doesn't have Enable Forecast turned on. The message reads "Measure is not configured to have a forecast".
• The series is Forecast and the classification's forecast is set to Amplify. An Amplify forecast is calculated automatically, so it can't be imported.
• The series is Actual or Forecast and the measure doesn't record actuals, because Record Actuals is off.

Dates

• Use any date Amplify can read, such as 2026-03-01 or 1 Mar 2026. A date inside a month is moved to the first day of that month.
• The date must fall within the measure's start and end dates.
• The date must be the start of a period of the measure's reporting cadence. A monthly measure takes the first day of any month. A quarterly measure takes the first day of a quarter. A financial year measure takes the first day of the financial year.

Quarters and financial years follow the instance's financial year end. For example, where the financial year ends on 30 June, it starts in July and the quarters start in July, October, January, and April. A row with any other month for a quarterly measure, or any month other than July for a financial year measure, is skipped.

Values

Enter the value as a plain number. A blank cell, or text such as $1,000, can't be read, and the row is skipped.

Creating the integration

To create the integration:

1. Open the initiative you chose.
2. Navigate to Tools > Integrations. The initiative's integrations are listed.
3. Click New Integration.
4. Enter a Name for the integration.
5. Select the Import Data Type: Measures, or Measure Values (Time Phased).
6. Click Create.

The Adapter is always Excel. Each integration imports one type, so create one integration for measures and another for their values.

Uploading the spreadsheet

To upload the spreadsheet:

1. On the initiative's integrations, click Run... next to the integration. A window opens.
2. Where the integration has been run before, select Upload New to choose a file, or Use Previous to use the last file again.
3. Choose the file.
4. Select Header? where the first row holds column headings.
5. Select the Sheet that holds the measures or the values.
6. Click Continue. The session page opens, with the rows from the sheet, and a preview starts.

The file must be an Excel file (.xlsx) of 5 MB or less, and the sheet can't exceed the row limit. Otherwise a message says so and Continue stays disabled. Only the last file uploaded is kept.

Mapping the columns

The first time you run the integration, you map each column of the spreadsheet to what it holds. Mapping is by column position, so it applies to whatever is in that column on the next run. It is saved as you make each change.

To map the columns:

1. Click Edit Mapping. A Type list appears for each column.
2. Select the Type for the column.
3. Set the fields that appear for that type, such as the Attribute or the Match on Attribute.
4. Repeat for each column that is imported.

A column left as No Action is ignored. A green tick on a column header means its mapping is valid. A red icon means it isn't, and hovering over it shows why.

Mapping measures

Map the columns like this:

• The initiative column — Type Parent Initiative, with Match on Attribute set to Name, Amplify ID or External ID.
• The classification column — Type Classification, with Match on Attribute set to Name or ID.
• The owner column — Type Owner, with Match on Attribute set to Name, Email or ID.
• The unit column — Type Unit, with Match on Attribute set to Name or ID.
• The name, start date, end date and cadence columns — Type Attribute Assignment, with Attribute set to Name, Start Date, End Date and Reporting Cadence. These are marked Required: in the list.
• The column that identifies existing measures — Type Identifier Lookup, with Match on Attribute set to ID or External ID.
• A description or custom field — Type Attribute Assignment with Attribute Description, or Type Custom Field, with the field chosen in Custom Field.
• Every other column — Type No Action.

Each of Classification, Owner, Parent Initiative, Unit and Identifier Lookup can be mapped to one column only. Each attribute and custom field can also be mapped once.

The session shows whether the mapping can create and update measures. Where it can't create, it lists the columns still needed. Until the mapping can either create or update, a message says the minimum requirement hasn't been met, and Preview and Import... are disabled.

Fallbacks for measures

A fallback gives a row a default when its cell is blank or has no match, so the row isn't skipped. A row that uses a fallback shows an amber warning.

• Fallback to Default Classification — uses the Default Classification you choose. The default must still be allowed under the initiative the row sits under.
• Fallback to Default User — uses the Default User you choose as the owner.
• Fallback to Default Initiative — places the row under the Default Initiative you choose. It must be at or below the initiative the integration is set up on, and can't be a program.
• Fallback to Default Unit — uses the Default Unit you choose.

Without a fallback, a row whose classification, owner, initiative or unit isn't found isn't created. Capital letters and spaces around the value are ignored.

Mapping measure values

Map the four columns like this:

• The measure column — Type Parent, with Match on Attribute set to Name, ID, or External ID.
• The series column — Type Attribute Assignment, with Attribute Series.
• The date column — Type Attribute Assignment, with Attribute Start Date.
• The value column — Type Attribute Assignment, with Attribute Value.
• Every other column — Type No Action.

Only one column can be mapped to Parent. This import type has no fallback option, and no Parent Type column: every row is for a measure.

The import can't run until all four columns are mapped. Until then, a message says the minimum requirement for creating or updating hasn't been met, and Preview and Import... are disabled. Where the series column isn't mapped, a message says "A definition for Code doesn't exist." Code is this message's name for the Series attribute.

Each row is marked with a plus icon, as if it were creating a value, even where it replaces a value that is already there.

Previewing and importing

Previewing the import

The preview checks every row against Amplify and saves nothing. It runs when the session opens. After changing the mapping, click Preview to run it again. Changing the mapping doesn't run it for you.

Each row shows whether it will succeed, and any errors or warnings. For measures, a plus icon marks a row that will create a measure, and a pen icon a row that will update one. A red icon on a cell marks a problem, and the row is skipped. An amber icon marks a warning, and the row still imports. Hover over an icon to read its message.

Where rows fail, a banner says how many rows were unsuccessful, such as "2 rows were unsuccessful." Click View these rows only. to show just those rows, and Show all rows. to return to the full list. To correct the spreadsheet, fix it and run the integration again.

Import... is disabled while a preview, import or mapping change is running, while the mapping is invalid, and until the mapping can create or update. Rows with errors don't disable it.

Importing the data

To import the data:

1. Click Import.... A confirmation opens.
2. Click Confirm.
3. Wait for the banner to report that the import has been completed.
4. Click End Session. The integrations list opens.

Until the session is ended, the integration shows Terminate in place of Run... and can't be run again. If a session was left in progress, click Terminate on the integrations list to end it.

Updating measures later

The same integration can be run again with another file. To update measures that already exist, map a column as Identifier Lookup, matched on ID or External ID. Each row then works as follows:

• Where the value matches an active measure, the row updates it. Archived measures aren't matched.
• Where it matches no measure and the mapping has every column needed to create one, the row creates a measure. An External ID in the cell becomes the measure's External ID. A mistyped identifier therefore creates a measure instead of failing.
• Where it matches no measure and the mapping can't create, the row fails.
• Where the cell is blank, the row creates a measure.

Where ID is used and the value matches nothing, the row creates a measure and the ID is ignored. The cell shows an amber warning.

An update changes only the mapped columns. A column set to No Action leaves its field as it is, and so does a blank cell. The following apply:

• Classification — can't change. The column is skipped with a warning.
• Parent Initiative — can't change. The column is skipped with a warning. A measure can't be moved to another initiative.
• Start Date and End Date — can change only in whole periods of the Reporting Cadence. A measure used by a benefit must still cover that benefit's dates, and a row that doesn't fails.
• Reporting Cadence — changing it rebuilds the measure's plan from the plan settings of its classification. Plan values loaded earlier are replaced.
• Owner and Unit — can change.

Give each measure an External ID and match on it with Identifier Lookup. The same file can then be run again to update the measures, and no measure is created twice.

Duplicate External IDs

Where the Identifier Lookup is matched on External ID, each External ID can appear on one row only. If the same External ID appears on several rows and doesn't exist in Amplify yet, the first row creates the measure and the later rows fail with a message that the External ID is the same on other rows. If the External ID already exists, every row with it updates that measure.

Updating values later

Run the same integration again whenever values change. Run it with Upload New to use a new file, or Use Previous to use the last one. The mapping is kept, so as long as the columns are in the same positions, you don't need to map them again.

• A value for a period that already has one replaces it. Running the same file twice gives the same result, and doesn't add anything twice.
• Periods that aren't in the file are left as they are. An import can't remove a value.
• Where the same measure, series, and date appear on more than one row, the later row's value is saved.
• To import rows that failed, fix them in the spreadsheet and run it again. Rows that were already imported are replaced with the same values.

Things to know

Periods without a value are saved as zero

Each series is saved without gaps. Where the spreadsheet skips periods between the measure's start date and the last period it imports, those periods are saved with a value of 0, unless they already have a value. For example, importing a single Actual for June saves 0 as the Actual for every earlier month the measure doesn't have one for.

Approvals

For how approvals work where values are entered in Amplify, see Managing Measures.

Benefits that use the measure

Once an import of measure values has finished, the benefits that use each measure are recalculated in the background. Their totals can take a short while to update.

History on the Timeline

Each imported value that differs from the value before it is recorded on the measure's Timeline, with the person who ran the import, the period and series, the value before, and the value after. A value that is imported unchanged isn't recorded. The same entries appear on the Timeline of each benefit that uses the measure. The entries are written in the background, so they can appear a short while after the import finishes. For filtering and searching the Timeline, see Activity Timelines.

Using measures in benefits

Measures feed the benefits that have a Benefit Formula. To link measures to a benefit by import, map Contributing Measures when importing benefits, matched on the measure's External ID or Measure Id. See Importing Benefits.

For the other types of import, see Importing Data.