
Acoléa
Specialized software application in the Aricie catalog.
Browse the four main areas of the Aricie business portal.
Software products developed and supported by Aricie.

Specialized software application in the Aricie catalog.

Specialized software application in the Aricie catalog.

Specialized software application in the Aricie catalog.

Specialized software application in the Aricie catalog.
Headquarters in Mureils with branches in Paris, Lyon, and Grenoble.
Migrating DNN content from one portal to another is a specialist job, not a simple database copy. DNN, formerly DotNetNuke, combines pages, modules, files, user accounts, roles, workflows and personalised content. A successful transfer preserves that structure while giving the destination portal a reliable foundation.
The move may support a rebrand, a new business application or consolidation of several websites. Its complexity depends on the DNN versions, installed extensions and custom code involved. A careful inventory, rehearsal and cutover protect search visibility, user access and day-to-day operations.
Begin with an inventory of pages, module instances, shared files, workflows, tags, redirects and user-generated content. Include hidden and inactive pages, because they can still be indexed or linked. Record where each item lives and whether it should be retained, rebuilt, archived or left behind.
Compare the source and destination environments: SQL Server versions, DNN compatibility, extension versions, custom modules, themes and licensed components. Review permissions by page, folder and module. DNN security roles may differ between portals, while personal data and account credentials need separate handling rather than a blind database copy.
DNN’s built-in export and import tools suit sites running compatible versions with standard modules. Content exports can move individual pages or modules, while extension packages can carry a module and its dependencies. Test the chosen mechanism against a small sample, since custom modules and personalisation rules may have limited export support.
A full database restore can accelerate a like-for-like move or create a clean staging copy. It is less suitable when existing portal content must be merged with another database, because tables, identifiers and extension structures can collide. Treat the restore as the starting point for a controlled merge, not the completed cutover.
For larger or heavily customised portals, combine these methods with scripts that transform content or map old identifiers to new ones. Move the file library deliberately: database records, physical files and page references must stay aligned. A URL mapping also matters if the new portal uses different domains, vanity paths or hostnames.
Create a staging environment, take tested database backups and freeze publishing shortly before the final transfer. Keep the original portal available for reference during development. Rehearse the runbook with the people who publish content, support users and approve changes, alongside the technical team.
Use these practical tools and checks to make each rehearsal repeatable:
Content and migration tools
Validation and cutover checks
After the rehearsal, correct content and permission differences before repeating the process. Compare page counts, file totals, sample forms, search results and sign-in journeys. Preserve a rollback point and agree a short publishing freeze for production.
Sydney and Melbourne are major hubs for Australian corporate and government work. If the source DNN portal is hosted in Europe, test response times from Australian offices and consider an AWS or Azure region in Sydney. Check whether the new hosting location meets the organisation’s data-residency and support requirements.
Remote teams in Perth and eastern states operate across time-zone gaps, so cutover times need Australian Eastern Time labels and clear ownership. A casual ‘we’ll have a proper look’ can sound reassuring without defining the next step. Assign each action a person, a due date and an acceptance test to prevent a fair bit of last-minute rework.
Australian buyers commonly combine in-house IT, local managed service providers and specialist software vendors. A French partner can fit that ecosystem, but contracts should state support hours, local escalation routes and subcontractors. Under the Privacy Act 1988 and Spam Act 2003, migrated forms, mailing lists and consent records need an owner and a compliant process. GDPR may also apply when a portal serves people in France or the EU.
Aricie is a French IT services company providing DNN solutions, custom software and professional training. Its applications include Acoléa, Adylic, AricieGrid and Budg-Immos, with teams in Mureils, Paris, Lyon and Grenoble serving organisations and professional partners. This DNN focus is useful for assessing extension dependencies, custom development and the training needed around a migration.
For Australian projects, confirm who will host the portal, provide after-hours cover and manage database access. Agree on data-transfer terms, especially when European personnel or infrastructure are involved. A joint delivery model with an Australian provider can preserve local response times while keeping specialist DNN knowledge close to the technical work.
Contact Aricie to request a DNN migration assessment and staging rehearsal. Share the source and target versions, extension list, approximate content volume and proposed cutover date. The team can work with your local partner to define the scope, schedule the test transfer and prepare a controlled go-live plan.