Migrating Granicus Permitting, Compliance, & Licensing (Amanda) from Oracle to SQL Without the Headaches

For many municipal, state, and provincial governments, Granicus permitting and compliance software has become the backbone of daily operations. It helps agencies streamline applications, track inspections, ensure compliance, and ultimately provide better services to citizens.

But behind the software sits the database, and for agencies still running Oracle, that foundation is becoming harder—and more expensive—to maintain. Rising licensing costs, shrinking in-house expertise, and the complexity of integrating Oracle with modern tools are prompting many agencies to consider a change.

One of the most common questions we hear at Vision33 is: “How big of a challenge is it to move our Granicus database from Oracle to SQL?”

The project can feel overwhelming. Agencies often imagine months of disruption, data integrity risks, and ballooning costs. The truth? While there are challenges, the migration process is easier than it appears, especially with the right planning and support. And the payoff? A lower-cost, more flexible system that positions your agency for the future.

This post explores why agencies are making the move, the challenges to consider, and a practical road map for getting there. We’ll also share how Volusia County, Florida, successfully completed its migration with Vision33’s support, achieving faster timelines, lower costs, and a stronger foundation for the future.

The Challenges: Why Agencies Hesitate

It’s natural for agencies to approach database migration cautiously. Permitting and compliance systems are mission-critical, and leadership can’t afford a misstep. Here are some of the most common concerns we hear:

• Fear of disruption. Agencies worry about downtime; with citizen services and compliance processes on the line, any outage feels risky
• Complexity of legacy systems. Many Oracle environments have been customized over the years, raising questions about how those customizations will carry over
• Uncertain costs. Tight public budgets make it difficult to commit to projects that seem expensive or unpredictable
• Skills gap. Internal staff may have deep Oracle experience, but not the same level of confidence in SQL

These challenges are real, but none are insurmountable. Agencies typically find that with proper planning, the migration is less disruptive and more rewarding than they expected.

Why SQL Makes Sense for Government Agencies

Migrating to SQL isn’t just a technical change—it’s a strategic move that unlocks multiple benefits:

• Lower operating costs. SQL licensing and support are generally less expensive than Oracle, freeing up budget for other priorities
• Cloud-readiness. SQL is the standard that Granicus has chosen for its cloud hosting solution, so moving to SQL is a necessary first step before going to its cloud solution
• Access to talent. SQL expertise is far more common in the IT workforce; this makes recruiting and training staff easier and reduces dependence on specialized consultants
• Integration power. SQL connects more easily to modern analytics platforms and other government technology solutions, improving reporting and system integration
• Performance. Properly configured, SQL often delivers faster performance and improved responsiveness in permitting systems

In short, moving to SQL sets agencies up to modernize operations, save money, and improve service delivery.

A High-Level Roadmap: How to Approach the Migration

So, how do agencies tackle the project? The key is breaking the work into manageable steps. Here’s a framework we’ve seen succeed:

Assessment & planning

• Preliminary conversion pass: Run it through a reputable SQL conversion/schema-assessment tool—many of which are free—to see what converts automatically, which objects (e.g., PL/SQL, stored procedures, triggers, sequences, and custom data types) will need manual attention, and to generate an initial effort estimate; this gives you immediate visibility into the work ahead and reduces guesswork
• Map integration between Amanda/Granicus modules and other systems
• Define goals: Whether cost savings, cloud readiness, or performance improvements

Data migration strategy

• Archive and clean up legacy data and legacy code before migration
• Use proven migration tools and scripts to map Oracle schema to SQL schema, informed by the results of your preliminary conversion
• Run test migrations early and iterate on fixes to surface issues before production cutover

Risk management & continuity planning

• Develop rollback procedures to minimize disruption
• Schedule cutovers during periods of low activity
• Prepare staff with training and communication to build confidence and reduce friction during the transition

Testing & validation

• Validate data integrity, workflows, and reporting
• Engage end users in acceptance testing to confirm usability
• Monitor performance closely after cutover and be ready to iterate

Cloud considerations

• If cloud adoption is on your road map, plan for it from the start—don’t treat cloud migration as an afterthought
• SQL simplifies both hybrid and cloud-native deployments

Real-World Example: Volusia County's Journey

One of the best examples of a successful migration is Volusia County, Florida.

After careful planning and internal analysis, Volusia County’s Land Information Systems (LIS) team realized the scope and time commitment of converting its Oracle database to SQL would be significant. The system contained:

• Hundreds of Crystal Reports
• Over 500,000 lines of Oracle PL/SQL code
• Thousands of standalone SQL statements

The LIS team knew this would be a massive technical challenge—and that success would require an experienced partner who understands Amanda inside and out.

Having worked with Vision33 on past projects, Volusia County knew where to turn. The LIS project leader, Jason Olsen, said:

“After planning our Oracle to SQL conversion and realizing the vast scope and time involved, the Volusia County LIS team decided to team up with Vision33. Having worked with them in the past, we knew they were the right company for the job. Vision33 proved to be an exceptional partner once again in bringing our vision to life. Through our combined efforts, we cut our original timeframe by more than 50%—accomplishing what once seemed impossible.”

The conversion required meticulous attention to detail. Every stored procedure, report, and integration point needed to be reviewed and adapted for SQL Server.

“The scope was substantial: hundreds of Crystal Reports, over 500,000 lines of Oracle PL-SQL, and thousands of standalone SQL statements all required conversion to T-SQL. We could not have achieved this without Vision33's expertise and support.”

Despite the scale, the project achieved its goals ahead of schedule—validating that even the most complex Amanda implementations can transition successfully.

According to Granicus, Volusia County has one of the most advanced Amanda deployments anywhere. If Vision33 could help them navigate this complexity, it demonstrates what’s possible for other agencies considering the same move.

The benefits were immediate and measurable:

• Project completed in less than half the expected time
• Enhanced digital flexibility and improved integration with modern tools
• Substantial budget reduction from Oracle licensing and maintenance savings
• Improved disaster recovery capabilities thanks to SQL’s built-in features

“Most enterprises are Microsoft-centric, and this is the logical move forward,” the Volusia County team said. “The benefits are significant: enhanced digital flexibility, substantial budget reduction, and improved disaster recovery capabilities.”

The LIS team led project management and overall strategy, while Vision33 delivered the technical expertise and problem-solving that made execution possible.

“Their entire team was eager, driven, and responsive throughout the process—working through complex technical challenges with skill and determination. We thank Vision33 for their outstanding partnership and tireless efforts in helping us achieve this milestone.”

The Result: A Future-Ready Platform

For government agencies, migrating Granicus PCL systems from Oracle to SQL may feel daunting at first. But with the right road map and experienced support, it becomes a straightforward project with long-lasting benefits:

• Lower costs and better resource allocation
• Stronger in-house expertise with a larger SQL talent pool
• Improved performance and easier integrations
• A simplified path to the cloud

Most importantly, it gives agencies the flexibility to keep delivering responsive, citizen-focused services without being constrained by aging infrastructure.

Closing Thought

Technology decisions in government aren’t just about IT—they’re about the ability to serve communities effectively and sustainably. Oracle has served agencies well in the past, but the future is about flexibility, cost efficiency, and cloud readiness.

For agencies considering this shift, the message is clear: The project is not as daunting as it seems. With a quick, early conversion assessment of your Amanda database and the right planning and support, migrating to SQL isn’t just possible—it’s a pragmatic path to modernization, savings, and future readiness.