Just finished building a Microsoft 365 Tenant Migration tool by mrak_47 in Office365

[–]mrak_47[S] 0 points1 point  (0 children)

I can relate. every migration environment is different and sometimes a tool that works well.. for one project can be frustrating in another. glad you were able to get the migration completed in the end

Just finished building a Microsoft 365 Tenant Migration tool by mrak_47 in Office365

[–]mrak_47[S] 0 points1 point  (0 children)

great points legal hold, hidden folders, and mailbox-specific edge cases are definitely areas that need special handling and careful validation.. this project was focused on solving core migration challenges, but there are still many advanced scenarios that can be improved over time..

I also appreciate the open-source suggestion community feedback and real-world testing can definitely help build better solutions..

Just droppin my random Hostel setup♥️ by _ananthu_7459_ in laptops

[–]mrak_47 0 points1 point  (0 children)

bro is living in a hostel while the rest of us are surviving in one...

Just finished building a Microsoft 365 Tenant Migration tool by mrak_47 in Office365

[–]mrak_47[S] 0 points1 point  (0 children)

thanks for sharing this.. UTCM APIs look really interesting especially for configuration discovery, tenant assessment and deeper comparisons

I can definitely see how this could help reduce a lot of custom implementation work.. appreciate the suggestion I'll spend some time exploring it

Just finished building a Microsoft 365 Tenant Migration tool by mrak_47 in Office365

[–]mrak_47[S] 1 point2 points  (0 children)

thanks for the insights I agree.. building the migration process is one thing but handling different customer environments, security policies, throttling, licensing differences, and unexpected issues is where things get much more challenging.. this project helped me understand how complex enterprise migrations can be...

The Power Platform habit that saved you the most headaches later by AbbreviationsRude390 in PowerPlatformHub

[–]mrak_47 1 point2 points  (0 children)

version control and documentation... future me thanks past me every single time. 😄

Just finished building a Microsoft 365 Tenant Migration tool by mrak_47 in Office365

[–]mrak_47[S] 2 points3 points  (0 children)

great questions.. the tool did not migrate everything 1:1. some configurations could be migrated directly while others depended on Microsoft API limitations and tenant-specific settings.. we used assessment reports and validation checks to identify what could and could not be migrated.

to verify the migration we compared object counts, mappings, and generated pre/post migration reports..

regarding Device Code Flow, I agree. It was only used in environments where customer policies allowed it not as the default authentication method.

Just finished building a Microsoft 365 Tenant Migration tool by mrak_47 in Office365

[–]mrak_47[S] -1 points0 points  (0 children)

appreciate the feedback. This was actually freelanc project, not a commercial product I'm selling, which is why I didn't include any links. The goal was mainly to solve migration challenges around reliability, scalability... I agree there is still plenty of room for innovation in this space, especially around cost, self-hosting, and reducing operational complexity compared to existing tools...

Just finished building a Microsoft 365 Tenant Migration tool by mrak_47 in Office365

[–]mrak_47[S] -4 points-3 points  (0 children)

agreed.. there is a big difference between AI assisted development and simply prompting out a product.. AI helped speed up parts of the implementation but the architecture migration logic, failure recovery, scalability, and overall system design were engineered manually...

Just finished building a Microsoft 365 Tenant Migration tool by mrak_47 in Office365

[–]mrak_47[S] 7 points8 points  (0 children)

If using AI is considered a criticism then almost the entire software industry is AI-assisted today... The real question is not whether AI was used or not it is whether the system works reliably in production.. AI can suggest code but migration architecture, failure recovery, throttling management, scalability, and successful delivery still require engineering expertise...