MIGRATE DATABASE TO ACCESS 365

Radise Lucas 0

Migrate 2013 Access database to Office 365 and share it with a group

2 answers

DBG 2,376 Reputation points

2025-02-14T16:10:55.9733333+00:00

Can you describe what problems you're having with the migration? Where are the members of the group located? Are you all situated in the same location and connected to the same LAN?
Please sign in to rate this answer.
Radise Lucas 0 Reputation points

2025-02-15T08:16:08.7566667+00:00

It as Microsoft Access Database (.accdb) that I now want to operate in the 365 environment
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
DBG 2,376 Reputation points

2025-02-15T14:40:03.2266667+00:00

Unfortunately, Access doesn't work well (if at all) in a cloud environment. One option for you is to keep the front end in Access and migrate the back end to Azure SQL or SQL Server or SharePoint.
Please sign in to rate this answer.
Sasha Froyland 1 Reputation point

2025-02-16T15:17:04.5733333+00:00

Based on our experience working with hundreds of enterprise Access applications, the core issue usually isn't Access itself - it's how organizations struggle to maintain and govern these applications effectively. Common challenges include:

Poor change management - When developers leave, the knowledge of how the system works often leaves with them, making future maintenance risky.

Integration complexity - Access databases often need to pull data from multiple enterprise systems (like your Oracle environment). Without proper documentation and maintenance, these integrations become fragile.

Deployment challenges - Enterprise environments require controlled deployment and version control, which Access doesn't handle well out of the box.

Security and compliance - While Access can be secured, enterprises often struggle to align it with their broader security and compliance requirements.

That said, Access is quite powerful when properly supported. The key is implementing enterprise-grade change management, documentation, and support processes around it. This allows organizations to maintain the rapid development benefits of Access while ensuring the applications remain maintainable and compliant with IT standards.

The solution typically isn't to immediately replace Access, but rather to properly support and gradually modernize these applications while maintaining business continuity. This often means keeping Access as the front-end while implementing better backend integration, deployment processes, and documentation.

Would you like to share more details about your specific integration challenges? That would help us provide more targeted recommendations.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

MIGRATE DATABASE TO ACCESS 365

2 answers

Your answer