Our Archiver for Notes product now also exports Notes Mail & Archives directly to Office 365, including On Demand.
This means that in a migration, Administrators might choose to migrate only recent Mail to Office 365 (e.g. the last 2 weeks, last 6 months etc), but also allow users to search and migrate any important older mail that they want to keep - employment contracts, legal information, personal mail, contact information etc.
This makes all historical Notes Mail available to users, without needing to migrate TB of unnecessary data. And this functionality can be used for as long as required.
For any other requirements, the tool also archives Notes Mail and Applications to NSF, PDF, XML, HTML and PST.
1. Administrator Archiving to O365;
2. Users can then search and export any further mail they require, from their Mail or Archives;
If you'd like to try this, please just download the demo version, then request a license key.
And for more information, please visit our Archiving page.
Showing posts with label lotus notes exporting. Show all posts
Showing posts with label lotus notes exporting. Show all posts
Monday, 10 October 2016
Tuesday, 19 April 2016
A new approach to migrating away from Notes
If you're migrating away from IBM Notes, here's a new option;
Instead of migrating ALL your Notes Mail data, migrate only the last X years worth (using any tool you want, but hopefully ours), and leave one Domino Server running HTTP to allow users to search and export their older mail, WHEN and IF they need it.
This saves migration resources, as users only export the mail they actually require. Users can search their Notes Mail & Archives via Browser whenever they want, as many times as they want, and export search results to PST, PDF, HTML or EML. For example a user could choose to export all their mail to the HR department, from a specific person/company, with the word 'legal' in the subject etc.
It also acts as a safety net - exporting the last X years of email provides 80% of what's required, and this approach returns the remaining 20% without needing to export TB of unnecessary data.
Powerful search functionality makes it easy for users to find the data they want, and they can export as many times as required.
The following screenshots show data exporting using a Web Browser (the same export options also apply in the Notes Client search).
1. Search
Each user sees only their own Mail and Archives. The Administrator controls options, labels, logos, and can modify the UI using CSS.
2. Export
From the results page, users select results to export, and the required format. The Administrator can show/hide each export format.
3. Status
A status of the export is shown in real time.
4. Fixes
If document fixes are required (e.g. to fix invalid email addresses), these are performed automatically.
5. Complete
Then the fixes re-exported.
6. Download
To finish, users simply download the exported files.
For more information, demos and downloads, please visit the FT Search Manager Migration Page.
Instead of migrating ALL your Notes Mail data, migrate only the last X years worth (using any tool you want, but hopefully ours), and leave one Domino Server running HTTP to allow users to search and export their older mail, WHEN and IF they need it.
This saves migration resources, as users only export the mail they actually require. Users can search their Notes Mail & Archives via Browser whenever they want, as many times as they want, and export search results to PST, PDF, HTML or EML. For example a user could choose to export all their mail to the HR department, from a specific person/company, with the word 'legal' in the subject etc.
It also acts as a safety net - exporting the last X years of email provides 80% of what's required, and this approach returns the remaining 20% without needing to export TB of unnecessary data.
Powerful search functionality makes it easy for users to find the data they want, and they can export as many times as required.
The following screenshots show data exporting using a Web Browser (the same export options also apply in the Notes Client search).
1. Search
Each user sees only their own Mail and Archives. The Administrator controls options, labels, logos, and can modify the UI using CSS.
2. Export
From the results page, users select results to export, and the required format. The Administrator can show/hide each export format.
3. Status
A status of the export is shown in real time.
4. Fixes
If document fixes are required (e.g. to fix invalid email addresses), these are performed automatically.
5. Complete
Then the fixes re-exported.
6. Download
To finish, users simply download the exported files.
For more information, demos and downloads, please visit the FT Search Manager Migration Page.
Monday, 22 February 2016
Saving Notes Search results to PDF
At the start of this year, we added PDF support to our FT Search Manager product.
This allows Notes search results to be saved directly as PDFs, either after a Discovery/Compliance search, or after normal Mail & Archive searching.
For example, let's say you have a legal requirement to provide copies of all email sent between your environment and 123.com during 2015.
1. Specified power users can run a Discovery/Compliance search across all mail files and archives in the environment, select the desired results, and export them to PDF.
2. Individual users can perform their own searches in response to an information-gathering request, select the relevant email, and export it to PDF.
Metadata is captured, the PDF format is easily controlled via stylesheets, and Administrators manage options for naming PDFs, export locations etc.
The same functionality applies to our Archiver for Notes product, which can now export Notes data directly to PDF (as well as NSF, XML, HTML, PST etc). So in the above example, Administrators could also create archiving criteria with an @formula and archive all matching emails to PDF, leaving the source data untouched.
For more information, demos & downloads, please visit the FT Search Manager page.
This allows Notes search results to be saved directly as PDFs, either after a Discovery/Compliance search, or after normal Mail & Archive searching.
For example, let's say you have a legal requirement to provide copies of all email sent between your environment and 123.com during 2015.
1. Specified power users can run a Discovery/Compliance search across all mail files and archives in the environment, select the desired results, and export them to PDF.
2. Individual users can perform their own searches in response to an information-gathering request, select the relevant email, and export it to PDF.
Metadata is captured, the PDF format is easily controlled via stylesheets, and Administrators manage options for naming PDFs, export locations etc.
The same functionality applies to our Archiver for Notes product, which can now export Notes data directly to PDF (as well as NSF, XML, HTML, PST etc). So in the above example, Administrators could also create archiving criteria with an @formula and archive all matching emails to PDF, leaving the source data untouched.
Monday, 22 June 2015
Exporting Notes Mail, Applications & Quickr to XML
Earlier this month, our Archiver for Notes product was extended to export Notes Mail, Applications and Quickr to HTML, in addition to exporting Notes Mail to Internet Formats and PST, and normal NSF archiving.
Exporting to HTML occurs via archiving to DXL, then transforming that DXL to HTML via XSLT Stylesheets. This allows storage of Notes data as static, non-proprietary HTML.
This process now extends further to transform DXL to XML, ready for use in other products. Example XSLT Stylesheets to do this are stored as Pages, and you can modify these or add your own.
This means you can export some parts of your Notes environment (e.g. Mail) to common internet formats or PST, other elements (e.g. old applications, IBM Quickr) to HTML, and specific newer elements (e.g. application data less than 5 years old) to XML for migration to other platforms.
The process is;
1. Select your target data, export method and stylesheet.
2. Stylesheets are stored as Pages in the Archiver Config database, so you can use these, customise them, or add your own.
3. Notes data is then exported to the target XML.
You can choose to leave the Notes data intact after exporting, meaning you can run the process as many times as you want.
For more information or a free, no-obligation trial version, please see the IONET Archiver for Notes.
Exporting to HTML occurs via archiving to DXL, then transforming that DXL to HTML via XSLT Stylesheets. This allows storage of Notes data as static, non-proprietary HTML.
This process now extends further to transform DXL to XML, ready for use in other products. Example XSLT Stylesheets to do this are stored as Pages, and you can modify these or add your own.
This means you can export some parts of your Notes environment (e.g. Mail) to common internet formats or PST, other elements (e.g. old applications, IBM Quickr) to HTML, and specific newer elements (e.g. application data less than 5 years old) to XML for migration to other platforms.
The process is;
1. Select your target data, export method and stylesheet.
2. Stylesheets are stored as Pages in the Archiver Config database, so you can use these, customise them, or add your own.
3. Notes data is then exported to the target XML.
You can choose to leave the Notes data intact after exporting, meaning you can run the process as many times as you want.
For more information or a free, no-obligation trial version, please see the IONET Archiver for Notes.
Monday, 8 June 2015
Archiving from Notes to HTML
Since March, it's been possible to use our Notes Archiving tool to archive Notes Mail to Internet Formats and PST, as well as perform normal Notes (to NSF) archiving.
We've now added the ability to archive Notes Mail and Applications to HTML and DXL/XML as well.
This allows Administrators to easily target specific Notes data, then process it based on their requirements, e.g. archiving to Notes itself, storing it in a non-proprietary format like HTML or XML, or migrating it for use with another application.
For example, to migrate to Outlook;
1. Your first archive criteria might first remove all mail with the phrase '[SPAM]' in the Subject.
2. Your second criteria might then archive all historical mail over 5 years old, and without the phrase '[HR]' in the Subject, to read-only HTML.
3. Your third criteria might then archive all mail 1-4 years old to PSTs named "Username" Notes Mail 2011 - 2014.
4. Your fourth criteria might archive all mail less than 1 year old to PSTs named "Username" Notes Mail 2015.
OR;
1. Archive all mail over 1 month old to PSTs named "Username" Notes Mail, leaving the original mail intact. This can be done over time without users even being aware of it, in order to migrate the majority of user data (as mail doesn't tend to change too much after the first month).
2. At a designated cutover date, archive any changes plus the remaining data, resulting in all Notes Mail being available in PSTs.
OR you could;
1. Select custom Notes applications and archive all data over 6 years old to HTML.
2. Archive all remaining data to DXL/XML, transform it via XSLT, and use it in another application.
There are multiple customisation options, and you can modify our stylesheets to suit your own processing requirements.
1. Select Archive Criteria (or you can just archive the entire database).
2. Exported Mail Results in HTML.
3. Exported Application Results in HTML.
4. Exported Mail Results in PST.
For more information or a free, no-obligation trial version, please see the IONET Archiver for Notes.
We've now added the ability to archive Notes Mail and Applications to HTML and DXL/XML as well.
This allows Administrators to easily target specific Notes data, then process it based on their requirements, e.g. archiving to Notes itself, storing it in a non-proprietary format like HTML or XML, or migrating it for use with another application.
For example, to migrate to Outlook;
1. Your first archive criteria might first remove all mail with the phrase '[SPAM]' in the Subject.
2. Your second criteria might then archive all historical mail over 5 years old, and without the phrase '[HR]' in the Subject, to read-only HTML.
3. Your third criteria might then archive all mail 1-4 years old to PSTs named "Username" Notes Mail 2011 - 2014.
4. Your fourth criteria might archive all mail less than 1 year old to PSTs named "Username" Notes Mail 2015.
OR;
1. Archive all mail over 1 month old to PSTs named "Username" Notes Mail, leaving the original mail intact. This can be done over time without users even being aware of it, in order to migrate the majority of user data (as mail doesn't tend to change too much after the first month).
2. At a designated cutover date, archive any changes plus the remaining data, resulting in all Notes Mail being available in PSTs.
OR you could;
1. Select custom Notes applications and archive all data over 6 years old to HTML.
2. Archive all remaining data to DXL/XML, transform it via XSLT, and use it in another application.
There are multiple customisation options, and you can modify our stylesheets to suit your own processing requirements.
1. Select Archive Criteria (or you can just archive the entire database).
2. Exported Mail Results in HTML.
3. Exported Application Results in HTML.
4. Exported Mail Results in PST.
For more information or a free, no-obligation trial version, please see the IONET Archiver for Notes.
Monday, 9 March 2015
New Export tool for Notes Mail & Archives
IBM (Lotus) Notes is an excellent product, but it's inevitable that some users will eventually migrate to other platforms.
The new IONET NSF Exporter allows users themselves to export local or server-based Notes Mail, Archives, Calendars, Tasks, Contacts and Journals to internet standard formats (*.eml, *.ics, *.vcf etc), then optionally to PST, ready for immediate use in Microsoft Outlook.
For an Administrator-run export via the Domino Server, please see the Archiver for Notes.
For example, after migrating to Exchange, users may still have local Notes Mail archives left on their PCs. The NSF Exporter allows them to migrate those databases to PST, at their convenience, and without requiring Server resources.
The tool requires a Notes Client only, exporting in the background. It can export local or server-based databases, running locally or from a Server.
Full fidelity is assured, including attachments, graphics & doclinks, for Mail, Calendars, Tasks, Contacts & Journals, with a range of options providing full control for the Administrator.
For a quick preview, please click the Thumbnails, then navigate around.
Default Settings

Export Settings

Description
The NSF Exporter allows users to export multiple Notes Databases to internet file formats, then optionally convert those files to PST. The tool can create one PST per NSF, or new PSTs when the existing export PST reaches a specified size.
Users create an export definition for each Notes Database they want to export, specify the export settings they prefer (e.g. skipping documents older than X days, skipping certain attachment types, decrypting documents etc), then just start the export. Administrators control what options users see.
The export process runs in the background of the Notes Client, leaving the Client available for other tasks, and a status of the export is displayed at all times, along with an estimated time to completion.
The user can also stop exporting at any time, restarting at a later time.
At the completion of the export, users can manage the exported files as they want, or simply open the resulting PST files in Outlook.
Key Features
For more information, downloads and demos, please visit the IONET NSF Exporter.
The new IONET NSF Exporter allows users themselves to export local or server-based Notes Mail, Archives, Calendars, Tasks, Contacts and Journals to internet standard formats (*.eml, *.ics, *.vcf etc), then optionally to PST, ready for immediate use in Microsoft Outlook.
For an Administrator-run export via the Domino Server, please see the Archiver for Notes.
For example, after migrating to Exchange, users may still have local Notes Mail archives left on their PCs. The NSF Exporter allows them to migrate those databases to PST, at their convenience, and without requiring Server resources.
The tool requires a Notes Client only, exporting in the background. It can export local or server-based databases, running locally or from a Server.
Full fidelity is assured, including attachments, graphics & doclinks, for Mail, Calendars, Tasks, Contacts & Journals, with a range of options providing full control for the Administrator.
For a quick preview, please click the Thumbnails, then navigate around.
Default Settings
Export Settings
Description
The NSF Exporter allows users to export multiple Notes Databases to internet file formats, then optionally convert those files to PST. The tool can create one PST per NSF, or new PSTs when the existing export PST reaches a specified size.
Users create an export definition for each Notes Database they want to export, specify the export settings they prefer (e.g. skipping documents older than X days, skipping certain attachment types, decrypting documents etc), then just start the export. Administrators control what options users see.
The export process runs in the background of the Notes Client, leaving the Client available for other tasks, and a status of the export is displayed at all times, along with an estimated time to completion.
The user can also stop exporting at any time, restarting at a later time.
At the completion of the export, users can manage the exported files as they want, or simply open the resulting PST files in Outlook.
Key Features
- Automatic Setup & Operation.
- Runs locally or server-based, in the background of the Notes Client, exporting local or server-based databases.
- Fully converts Mail, Archives, Calendars, Tasks, Contacts and Journals, including images, attachments & doclinks.
- Does not require Microsoft Outlook.
- Creates one PST per NSF, or multiple PSTs based on size.
- Allows users to process or skip specific attachment types.
- Allows users to export data based on date.
- Allows users to export data based on size.
- Allows users to decrypt documents during export.
- Includes real-time progress display.
- Supports Unicode character migration, including multiple character sets.
- Retains meta data and Folder structures.
- Leaves original data intact.
- Fully translatable UI.
- Automatically attempts to fix known errors.
- Logs all errors and actions.
For more information, downloads and demos, please visit the IONET NSF Exporter.
Subscribe to:
Comments (Atom)

















