# Feature - Update a compliance package with an import
**URL:** https://discussions.eramba.org/t/feature-update-a-compliance-package-with-an-import/262
**Category:** Forum - Software
**Created:** [May 5, 2017, 8:49am UTC](https://discussions.eramba.org/t/feature-update-a-compliance-package-with-an-import/262 "2017-05-05T08:49:51Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@eramba](https://discussions.eramba.org/u/eramba)
#### Post date: [May 5, 2017, 8:49am UTC](https://discussions.eramba.org/t/feature-update-a-compliance-package-with-an-import/262/1 "2017-05-05T08:49:52Z")
Suppose you have HIPAA Trust 8.0 , you have related internal controls and policies. Now 8.1 comes out, how do you go around that update? Right now is a manual job, you need to edit the compliance package using Compliance Management / Compliance Packages.
We need a feature that allows me to import the new version and update the existing content. This is not simple as there could multiple situations:
- OLD has items NEW does not have
- NEW has items OLD does not have
- NEW and NEW has the same items but different content (title, description)
How we go around this … not sure. Ideas anyone?
---
### Author:  [@njaehnert](https://discussions.eramba.org/u/njaehnert)
#### Post date: [May 5, 2017, 2:57pm UTC](https://discussions.eramba.org/t/feature-update-a-compliance-package-with-an-import/262/2 "2017-05-05T14:57:27Z")
This is a difficult one because for historical purposes, you may have been compliant with (using your example) HITRUST 8.0. Now, HITRUST has changed one of the controls and made it more strict, so in 8.1 you do not comply.
Whatever we decide to do in Eramba should definitely keep the historical/previous version for reference. I have a bunch of other thoughts/ideas around this topic but unfortunately have to run off to a meeting. Will try to put more down to paper and post them here later.
Thanks,
-Noah
---
### Author:  [@eramba](https://discussions.eramba.org/u/eramba)
#### Post date: [May 8, 2017, 11:15am UTC](https://discussions.eramba.org/t/feature-update-a-compliance-package-with-an-import/262/3 "2017-05-08T11:15:58Z")
Exactly, for that reason we put the “Duplicate” option:
This “Copies” a compliance package and all its controls, policies relationships (done trough Compliance Management / Compliance Analysis) on a copied item.
Then you can work on the original package in peace (you have a copy)…I’ll think on the logic on how imports could work and report back here in a while.
---
### Author:  [@eramba](https://discussions.eramba.org/u/eramba)
#### Post date: [May 24, 2017, 12:25pm UTC](https://discussions.eramba.org/t/feature-update-a-compliance-package-with-an-import/262/4 "2017-05-24T12:25:46Z")
[https://github.com/kisero/eramba\_v2/issues/616](https://github.com/kisero/eramba_v2/issues/616)