Move spreadsheet data into your portal with Adylic

Australian teams often collect operational information in Excel workbooks before sending it through a shared drive, inbox or project folder. A Sydney head office may hold the master list while branches in Melbourne and Brisbane update local copies. The result is valuable data spread across too many versions.

Adylic's Data Import Tool helps teams migrate spreadsheet records into a portal managed with DotNetNuke. It reduces repetitive data entry by using rows already captured in a workbook, while Aricie aligns the import with how the portal will be used day to day.

A smooth migration depends on preparation rather than the import button. Field names, dates, identity checks and access controls need attention before bulk records are loaded, particularly when files contain customer details, Australian dollar amounts or information governed by Australian privacy rules.

Why spreadsheets become a portal bottleneck

Spreadsheets remain useful because people can filter, sort and review them quickly. They also support offline work during busy trading periods or weak connectivity. Those flexible editing habits can create inconsistencies that only become visible after records enter a shared portal.

Common problems include duplicated contacts, renamed columns, merged cells and totals imported as ordinary records. A workbook prepared for internal reporting may also contain notes, formulas or presentation rows with no place in the live database.

The import workflow changes the task from re-keying to structured preparation. A clean source file, deliberate field map and controlled test batch help ensure portal users receive accurate, searchable information rather than a direct copy of an inconsistent workbook.

Prepare source files before importing

Begin by identifying the authoritative version of the workbook. Check that the header row contains genuine text, each record occupies one row, and no totals or explanatory lines appear beneath the data. Agree on the final submission before mapping columns when several offices contributed records.

Standardise values without discarding useful context. Check day-first dates such as 04/07/2026, AUD values with dollar signs and comma separators, GST-inclusive amounts, and Australian identifiers such as ABNs or ACNs. Keep the original for audit purposes, but prepare a separate import file rather than editing the only retained copy.

A dependable migration checklist

Assign an owner to approve the source file and document which version will be processed. A short review before loading data can prevent delays, incorrect records and unnecessary cleanup inside the portal.

The following checks create a repeatable import process that can also be used for later updates:

• Archive the approved source with a clear version date and location.
• Confirm the required file format, delimiter and text encoding before processing.
• Use consistent column headings and remove merged cells or multi-row headers.
• Separate genuine records from totals, notes, formulas and blank rows.
• Validate required fields, date formats, currency values and identifiers.
• Import a small sample first and reconcile its results with the source.

Map fields and clean the data

Field mapping connects spreadsheet columns to their destinations in Adylic. This is where column aliases, blank values and inconsistent labels must be resolved. A repeatable mapping document prevents the same cleanup from being recreated whenever a new workbook arrives.

Clean data according to the portal's business rules rather than visual preferences. For example, standardise Australian addresses with state abbreviations such as NSW, VIC and QLD, format local phone numbers consistently, and decide which source values count as duplicates. Keep the transformation rules outside the spreadsheet so every update follows the same logic.

After migration, portal users often need to inspect particular groups of records. If that search work happens in AricieGrid, the advanced filtering tutorial demonstrates how power users can refine results without returning to the source workbook.

Validate records and protect sensitive data

Compare record counts, totals and representative samples before publishing imported data. Review the first and last rows, key fields and records containing unusual characters or formatting. Where possible, have a business user reconcile a sample against the approved spreadsheet.

For organisations covered by Australian privacy legislation, the Privacy Act 1988 and Australian Privacy Principles may apply to personal information held in the spreadsheet. The Notifiable Data Breaches scheme also sets notification requirements for qualifying incidents. Identify free-text notes containing health, financial or other sensitive details, restrict access to the migration files and securely retain or dispose of temporary copies.

A staged approach supports safer testing. Load a limited batch, check portal permissions and verify that searches, exports and user workflows behave as intended. Production data should enter the portal only after the team has confirmed that the mapping, validation and access settings are correct.

Roll out the migration with confidence

Aricie is a French IT services company with offices in Mureils, Paris, Lyon and Grenoble. Its DotNetNuke solutions, custom software development and professional training support a controlled rollout, from preparing the source data to helping staff maintain the portal after launch.

Start by sending Aricie a representative spreadsheet, a sample of the intended portal fields and any privacy constraints. The team can help design a staged migration, map the data and train administrators. Contact Aricie to arrange an Adylic Data Import Tool demonstration and agree on a practical test plan before production records are loaded.