Good Morning, We woke up this morning to the new Import Interface, thankfully, the legacy interface is still available, but it has generated a great deal of anxiety on the future design of this feature. Needless to say, we are waiting with bated breath for the release notes and webinar. I wanted to pre-emptively emphasize the importance of the legacy Import feature’s functionality and the value it provides administrators. For us, loss of any of those legacy functions would be a huge negative impact to our maintenance operations. We need the import feature to continue to: Allow us to maintain static specs - we perform daily imports across a number of Apricot sites - we need to be able to quickly generate a specs document to our partners It helps to know field IDs, validation and data requirements when generating a spec - it is very easy to get this information when generating specs in the legacy interface. We need to be able to revert imports if there were issues/errors. It is very helpful to be able to see the imported/updated records so user can check a few after import It is very helpful to confirm the uploaded file for import when troubleshooting. It’s very helpful to download skipped or error’d rows so we can proceed with the import and resolve those issues when able.IF WE have to map fields every time we perform an import - that’s just untenable. It will exponentially increase the time needed for our daily maintenance activities. And creates significant opportunity for errors.IF we cannot generate specs for import files easily - we will need to laboriously, manually create specs.If we cannot validate and trace back completed imports to their original import source, resolving errors will become a monumental task. If we cannot manage errored rows efficiently - we risk missing importing critical data. How long will the legacy interface be supported? What is Bonterra’s plan for the new interface to ensure we are not losing critical functionality with the import feature?

Explorer

Solved

New Import Interface - 9/24/2026

Forum|Forum|6 days ago
September 24, 2026
11 replies
102 views

Good Morning,

We woke up this morning to the new Import Interface, thankfully, the legacy interface is still available, but it has generated a great deal of anxiety on the future design of this feature. Needless to say, we are waiting with bated breath for the release notes and webinar.

I wanted to pre-emptively emphasize the importance of the legacy Import feature’s functionality and the value it provides administrators. For us, loss of any of those legacy functions would be a huge negative impact to our maintenance operations.

We need the import feature to continue to:

Allow us to maintain static specs - we perform daily imports across a number of Apricot sites - we need to be able to quickly generate a specs document to our partners
It helps to know field IDs, validation and data requirements when generating a spec - it is very easy to get this information when generating specs in the legacy interface.
We need to be able to revert imports if there were issues/errors.
It is very helpful to be able to see the imported/updated records so user can check a few after import
It is very helpful to confirm the uploaded file for import when troubleshooting.
It’s very helpful to download skipped or error’d rows so we can proceed with the import and resolve those issues when able.

IF WE have to map fields every time we perform an import - that’s just untenable. It will exponentially increase the time needed for our daily maintenance activities. And creates significant opportunity for errors.

IF we cannot generate specs for import files easily - we will need to laboriously, manually create specs.

If we cannot validate and trace back completed imports to their original import source, resolving errors will become a monumental task.

If we cannot manage errored rows efficiently - we risk missing importing critical data.

How long will the legacy interface be supported?

What is Bonterra’s plan for the new interface to ensure we are not losing critical functionality with the import feature?

Apricot

Best answer by Molly Kraus

Hi Deanna,

Thank you for sharing this so thoughtfully - appreciate you taking the time.

First, some reassurance: the legacy interface isn't going anywhere anytime soon. It will remain available while the new experience continues to be developed, and we will provide advance notice to help you and your team plan accordingly before any transitions happen.

We have documentation in the works that will give much more detail on what the new imports experience includes. Here are some of the topics that will be covered:

- How the workflow guides you through mapping your CSV column headers to the corresponding fields in Apricot
- How validation works before records are created, and how to correct errors directly in the tool
- Where to find and download error files so you can address issues and keep your import moving
- How to use import history to track and review completed sessions

In the meantime, if you haven't already, we'd encourage you to log the specific capabilities that are most important to you to see in the new experience in the Ideas Portal. That's one of the best ways to help us understand what to prioritize as we continue building.

Thank you again for your thoughts and being an engaged member of this community!

Molly KrausAnswer

Bonterran

Hi Deanna,

Thank you for sharing this so thoughtfully - appreciate you taking the time.

First, some reassurance: the legacy interface isn't going anywhere anytime soon. It will remain available while the new experience continues to be developed, and we will provide advance notice to help you and your team plan accordingly before any transitions happen.

We have documentation in the works that will give much more detail on what the new imports experience includes. Here are some of the topics that will be covered:

- How the workflow guides you through mapping your CSV column headers to the corresponding fields in Apricot
- How validation works before records are created, and how to correct errors directly in the tool
- Where to find and download error files so you can address issues and keep your import moving
- How to use import history to track and review completed sessions

In the meantime, if you haven't already, we'd encourage you to log the specific capabilities that are most important to you to see in the new experience in the Ideas Portal. That's one of the best ways to help us understand what to prioritize as we continue building.

Thank you again for your thoughts and being an engaged member of this community!

Naomi Katz

Active Advisor I

Thank you for posting this!! We do a weekly series of imports that involves running 2 imports, downloading skipped records and created record IDs, mapping that to an excel file, and then doing 2 more imports. We have this process really well nailed down and removing any of the capabilities mentioned above would significantly impact this process.

Please do not make the core features of the import tool less accessible!

I also urge you to leave the downloading of skipped / created records within each import.

I’m not sure why this feature is being updated - I’m sure there’s a reason - the legacy version is great. It would be a real shame to have one of Apricot’s most functional features be downgraded for the sake of a new UI.

We’ll certainly be using the legacy version until the tutorials are available and we have the capacity to test the new version out.

It would be really great if we would get alerts or emails when core features like this are going to be changed.

Molly Kraus

Bonterran

Hi Naomi, the specifics here are really helpful — this kind of detail that helps us identify where the new experience still has room to grow. The legacy interface remains available, and you are welcome to keep using it in the meantime. When you do get a chance to test the new one, we'd love to hear how it holds up against your process.

Olivia Mangini

Rising Star I

I COMPLETELY agree with you Naomi- I just tried to play around with the new interface and it does not make any sense. How are you expected to have the CSV you want to import ready before getting a structure form made with your fields. This whole mapping thing seems to defeat the purpose of having a form made for you based on what fields you said you wanted to include. I am not happy with this. Is this even a problem that people had? why was this change made?

Naomi Katz

Active Advisor I

@Molly Kraus or @Rebekah Eslao - Are you able to give us some context around why this feature is being updated? It’s one of the most reliable and useful features in Apricot so it would be helpful to understand some of the context around why it’s being modified.

Olivia Mangini

Rising Star I

I think this would be helpful for me as well.

Molly Kraus

Bonterran

Hi Olivia - Thanks for taking the time to explore the new interface and share your reaction. Knowing that having a template up front is an important part of your workflow is exactly the kind of input that helps us as we continue expanding the new tool to support a wider range of approaches. In the meantime, the legacy interface is still there for you.

Charlie Payne

Explorer

I want to chime in an echo the concerns of Naomi and Olivia. I use the import feature somewhat regularly and all the features in the legacy import are useful and needed in this new interface.

A couple of questions:

When the legacy interface is phased out, will automatic imports be impacted?
Was the change to the import interface communicated prior to it being rolled out?

DavidH

Rising Star I

I tried using the new interface and switched back after like 5 minutes. The import system was/is powerful, and it kind of surprises me that this is what the development team is changing. I have a laundry list of functionality requests I’m about to submit here and none had to do with the import system. I have 400+ imports on the old system and used it exclusively to migrate our data to Apricot with over 300,000 records and it worked very well. That was build off of the import CSV templates the import tool provided.

Looking at other comments here I want to talk about core functionality I found profoundly useful in the now “legacy” system.

CSV exports of skipped, or failed record imports
CSV exports of created records including the record ID
Clickable links when new record are imported.
Seeing the system field values in the CSV import template
Getting a static CSV template that we could build automations and forms off of if we needed some sort of scheduled import in the future, which is a very real possibility
Being able to update existing records and import new records in the same import.
Seeing accepted values per column/field
Easy revert of imports for whatever reason
Easy labeling of imports

And that’s off the top of my head.

Sign up

Login with your EveryAction email and password to access the community

Login to Bonterra Central

Login with your EveryAction email and password to access the community